karl krach

just for the record, i noticed something very strange: i work on a huge patch, which, at start, loads some simple graphics on the gpu. all worked well until i set my main output jit.window at startup to @floating 0: if i start now, i get the message "jit.gl.texture: error binding texture to target: GL Error: Invalid operation" over and over and the graphics seem to get swapped and some do not load at all.

however, once i enable the floating attribute (even if already running), all turns back to normal and stays that way, even if i later disable floating again. i didn't check wether that's related but the only other thing i recently changed in that area: the jit.window is set to @grow 0.

hi,
just for the record, i noticed something very strange: i work on a huge patch, which, at start, loads some simple graphics on the gpu. all worked well until i set my main output jit.window at startup to @floating 0: if i start now, i get the message "jit.gl.texture: error binding texture to target: GL Error: Invalid operation" over and over and the graphics seem to get swapped and some do not load at all.
however, once i enable the floating attribute (even if already running), all turns back to normal and stays that way, even if i later disable floating again. i didn't check wether that's related but the only other thing i recently changed in that area: the jit.window is set to @grow 0.

small-but-weird-open-gl-bug

little update: i did not change anything related, just replaced some patch cords with send/recieve. however, now it works the other way around: i get the error if i start with @floating 1, but not with @floating 0. again, if i switch that later (once everything is running) all works well.

little update: i did not change anything related, just replaced some patch cords with send/recieve. however, now it works the other way around: i get the error if i start with @floating 1, but not with @floating 0. again, if i switch that later (once everything is running) all works well.
hm hm...


hi karl... im not alone in the world! i been having exactly the same issue, big patch with a lot of subpatches with diferent scenes and suddenly start to get that bind errors messages when i enable scenes with slab chains... not always but sometimes...

in my case what solve the problem was erase from the patch the jit.phys.world object.... weird... but since then no more crashes...

seems theres something deep on this.. i forward the case to c74 support...

hopefully you can help us track these issues down.

yes, please get in touch with support.
hopefully you can help us track these issues down.


small but weird open gl bug?