Win11, 2025.33070. Loading the shipped palette component Techniques/geoPanel.tox from Python can permanently stall the frame loop: loadTox returns, then within 1-2 frames no frame advances again. UI frozen.
The core operation is just:
w = op('/').create(baseCOMP, 'wedge_test')
w.loadTox(app.samplesFolder + '/Palette/Techniques/geoPanel.tox')
w.destroy()
but run bare from the textport it usually survives, which is odd. The attached .toe reproduces it reliably; what we have observed:
- Bare textport run of the three lines above: no stall (repeatedly).
- Same load inside a scan-style loop (wrapper created in a child COMP,
timeline-state save/restore around the load, a small fsync’d file write
between loads): stalls, typically on the first load after open. - A session with the textport fullscreened over the network editor
survived repeatedly; sessions with the network editor visible stalled –
maybe meaningful given geoPanel runs panel.interactTouch/interactMouse/
setFocus every frame from execute DATs the moment its network exists - Same steps are fine on 2025.32820, and geoPanel.tox is md5-identical
between the two installs – runtime regression, not palette content. - Tools/chromaKey.tox reproduces it too; the rest of the palette loads
clean. Hit via Embody’s palette scan (loads each component to
catalog it); two machines froze identically.
Attached .toe: two DATs. On open it runs up to 30 load/destroy rounds with
heartbeat prints between, and appends each step to repro_log.txt beside the
.toe (survives the freeze). 32820 completes all rounds; on 33070 it stalls
on round 1 here – prints stop, the generated log file (txt) shows the last step reached.
TD33070_paletteLoad_wedge_repro.toe (4.8 KB)