11-08-2024, 05:38 PM
Hey Tyson, sorry we didn't get back to you.
3ds wasn't actively creating minidumps, so we've been stuck.
Our pipeline dev has been trying to debug it the last couple of days and they've attached to the process using WinDbg and managed to get a somewhat consistent stack trace, paired with the Redshift log cutting off early - while loading Tyflow objects from a certain setup. Please see images attached.
We're not really sure if tyFlow is the cause, but would appreciate any guidance, hopefully, something screams out to you from the images. (Note it's always the two tyFlow_2022_render!NodeAndAnims::SetNode+ at the same memory addresses if that means anything to you)
3ds wasn't actively creating minidumps, so we've been stuck.
Our pipeline dev has been trying to debug it the last couple of days and they've attached to the process using WinDbg and managed to get a somewhat consistent stack trace, paired with the Redshift log cutting off early - while loading Tyflow objects from a certain setup. Please see images attached.
We're not really sure if tyFlow is the cause, but would appreciate any guidance, hopefully, something screams out to you from the images. (Note it's always the two tyFlow_2022_render!NodeAndAnims::SetNode+ at the same memory addresses if that means anything to you)