What is jit_ob3d_dest_name_set ?
Does any of you Max insiders and jitter wizards know what jit_ob3d_dest_name_set could refer to?
This is the last task I get in crash reports (EXC_BAD_ACCESS (SIGSEGV)). The funny thing is that the crash can be triggered with various actions, which are at first glance completely unrelated to each other, and don't always provoke a crash, but every time it does, the last task is alwayjit_ob3d_dest_name_set. Sometimes, by looking at the previous tasks, it seems related to loading equirectangular maps into jit.gl.environment, sometimes to some jit.gl.slab, sometimes it's harder to say.
It comes from a gigantic patch with dozens of subpatchers and many interdependencies, so this + the irregularities of the crashes makes them very difficult to troubleshoot. The only constant is this task 0 jit_ob3d_dest_name_set .
I struggle to find an actual culprit, so I would be grateful for any hint!
Running Max 9.0.5 with macOS 14.7.4 on Apple silicon chip.
This is the the drawto attribute setter function, called whenever the drawto of an ob3d (ie jit.gl object) is changed, either implicitly by internal logic or explicitly by the user.
As always feel free to contact us directly with a crashing patch.
Thanks Rob, that helps a bit. What could that mean in the context of a sigsegv crash?
That the context to draw to doesn't exist anymore?
Or that the ob3d object for which the drawto is being changed has disappeared in the way?
Or something else...
If I manage to isolate the issue I'll definitely try to reproduce it in a smaller patch!
impossible to say without taking a peak