Crash (null write in libTD.dll) with a per-frame animated Transform POP - 2025.32820 / 2025.33230, Windows

Bugs
1

Builds: 2025.32820 and 2025.33230 (clean install, no third-party plugins)
OS: Windows 11 (10.0.26200)
Machine: Alienware x16 R1, Intel Core i9-13900HK, 32 GB LPDDR5
GPU: NVIDIA GeForce RTX 4090 Laptop GPU (driver 32.0.16.1714; also reproduced on 32.0.15.9608)

Repro (minimal)

Script SOP (single-line stroke text, ~270 points / 24 line strips) → SOP to POP → Transform POP (rz / sx / sy driven by absTime.seconds expressions) → Geometry COMP (Select POP) with Line MAT → Render TOP.

TD crashes within 30 s to ~11 min.

Observations

  • Static POP (no per-frame change) rendered with an animated camera (so it still renders every frame): no crash in 15 min.
  • Same crash when the Transform POP is replaced by a GLSL POP (no samplers).
  • Hybrid graphics on/off (BIOS, dGPU-only) and which display the window is on make no difference.
  • 2025.33230: Fatal Error dialog, TouchDesignerCrash.2025.33230_1.dmp written (attached). Exception 0xC0000005, write to address 0x0 at libTD.dll+0x1f0d9db.
  • 2025.32820: the crash handler itself seems to hang while writing to the hidden console (main thread in fwrite -> WriteFile -> NtWriteFile), so the process shows as “Not Responding” instead of showing the dialog, and no .dmp is written.
  • The same kind of hang/crash also happened in larger projects that use POPs animated every frame (Delete POP / GLSL POP chains feeding Script SOPs), at random points in pure-Python code, which looks like memory corruption surfacing later.

I can provide the minimal .toe if needed.

Thanks!
TouchDesignerCrash.2025.33230_1.zip (251.4 KB)

2

Hello @tsumiki.room

Sorry to hear that you are experiencing this crash. The crash dump indicates that something wrong is happening when allocating some string memory. Would it be possible to share that minimal .toe file so that we can try to replicate?