← all posts site ↗

orca slicer crashed on slice

opened an orca slicer project with a couple of things imported on a plate, selected the plate, hit slice, and it crashed. every time. saving crashed too. it felt like my project or my machine was the problem, but it was neither. this is a known upstream bug in orca slicer 2.4.2, and the crash signature matches it exactly.

the segfault happens inside mesa's graphics driver, in the code that renders plate thumbnails, called from the preview focus handler. the slice engine never even ran. the log just ends at the preview select and the thumbnail render finishing. the root cause is a context mismatch. the slicer renders thumbnails into an offscreen framebuffer without making its own graphics context current first, and its embedded web engine has a dmabuf renderer with its own context in the same process. when that foreign context is current, the slicer's shaders and buffers do not exist, the draw call runs with no index buffer, and the driver reads the offset as a pointer and dies. that is also why saving crashes: save renders thumbnails too.

the workaround is one environment variable that disables the web engine's dmabuf renderer. i dropped it into a launcher override so the app starts with it every time, and confirmed the running process had it. slicing worked again immediately. the real patch ships in version 2.5.0, so once that lands this whole class of crash disappears and the workaround can come out. the takeaway is the usual one. when an app dies with a driver segfault, check upstream before you blame your own project. two identical crashes with clean logic on your side is a fingerprint, not a coincidence.