Hi Derivative Team,
I have isolated a issue where the Engine COMP permanently corrupts .tox files into an infinite XML parsing loop (TiXmlNode::NextSibling).
The Setup:
-
Context: Using an Engine COMP to run a Slamtec CHOP.
-
Settings: Engine Clock set to Independent. There is no viewer or ./out1, made it empty.
-
Internal: The
.toxcontains noOut TOPs(visuals are handled via Spout).
The Bug: Despite setting the Clock to Independent and disabling Texture Output, the Engine process eventually deadlocks. WinDbg analysis confirms the thread is waiting on: libTD!TER_TouchInstance::hasExportableTimelineSemaphores → msvcp140!_Cnd_timedwait
Observation:
-
The “Zombie” Check: The Engine continues to block waiting for a Timeline/Texture Semaphore even though I have explicitly disabled Texture Output and set the clock to Independent. It seems the Engine does not correctly disengage this check, leading to a deadlock when the Slamtec driver introduces timing irregularities.
-
Corruption: Once this deadlock occurs, the
.toxfile structure becomes corrupt. Both the Main Process and the Engine subsequently freeze in an infinite loop atlibTD!TiXmlNode::NextSibling. genAI says I need to rebuild the engine file from scratch to prevent this error from happening again.
The freeze is triggered every 40 minutes or so only when I try to go in and out of bases or work on the project, it never occured when I did a dry run for 16 hours+. So I hope this won’t happen in production haha. Can’t really share a tox since the project is pretty massive with a lot of assets ![]()
Best,
Robert