-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux OpenGL: PrusaSlicer segfaults immediately after slicing complex objects #5889
Comments
Those do look similar. Curiously, both of them are also on AMD cards (I'm using Given that it only sometimes happens, and is apparently dependent on the sliced model's complexity, my spidey sense tells me this might be a race condition. |
I have a very similar problem #5745, but unfortunately your two solutions don't fix it for me. With software rendering it will outright crash upon start, with the DRI disabled it will still crash after slicing. And yes, it has to be something related to the Mesa/amdgpu (like 20 something) driver, as with an older version of it I didn't have that issue in the past. And with PrusaSlicer 2.2 it just works, but it's missing features, obviously. |
I have been having the same issue since I started using a vega 64 appimage and built from source how can I launch with software rendering only ? |
Read the issue description, under "known workarounds" |
Same issue, I have an AMD gpu too. Only fix for complex objects for me is to use LIBGL_ALWAYS_SOFTWARE=true (thanks @tullo-x86 ). Fortunately I have a good CPU but it's still painful. |
@cubiq did you try EDIT: Something changed in my environment (most likely Mesa) — the crash now happens even with DRI3 disabled; all that works for me is forcing software rendering. |
yeah I tried, doesn't work unfortunately |
I'm having this issue as well on my swaywm setup. None of the listed fixes have worked, but I am able to slice very simple models as was also mentioned. I maxed out logging and it seems to crash immediately after refreshing extrusion paths. |
@DavidBittner which graphic stack are you on? Mesa probably? These problems started for me after a certain version of Mesa and affects all versions of Prusa Slicer >=2.3 (including RCs and alpha/beta). 2.2 works well though, but it is outdated. For me it always crashes when calling I can slice some things, but most things just end up in a crash and there is no pattern besides that if it crashes once for a specific object and specific settings, it will always crash. But with other settings, e.g. other infill value or other layer height, it might not crash. Edit: |
You were right about it being mesa. I went ahead and downgraded mesa a bunch to try and narrow it down and the crashes actually did stop. It was at version mesa-21.0.0.-1 that they stopped happening. I guess I will just keep mesa a bit downgraded for now until an update comes out. But either way, downgrading mesa seems to have fixed the problem for me. |
Can you guys please try out the new 2.3.1 patch release to see if it helps? It has in #6345 (comment). Thanks. |
works for me now, thanks for the heads up @lukasmatena |
@lukasmatena Unfortunately, the v2.3.1 RC did not completely solve the issue on my machine. Benchy can now be sliced, but other complex models still fail. However, the workaround (disabling DRI3 and relying on DRI2) has started working again after a recent Mesa patch broke it. This plays into my suspicion that the underlying issue is a race condition. |
I need to test it more before I can say for sure that it has fixed the crashes completely, but as of now it slices a couple of things that 100% crashed before. No crashes yet - that is really cool! Out of curiosity, which commit did fix the issue? Edit: Edit 2: |
damn, still got some crashes. much less than before though vase mode is also a no-no as @smirgol noted. Also tried the latest version |
We cannot support Linux OpenGL driver issues. Closing. |
Known workaround
I managed to work around the segfault by disabling DRI3 in LibGL:LIBGL_DRI3_DISABLE=true prusa-slicer
. I'm not sure why this works, only that it does on my machine.Another option is to force Mesa to use software rendering (
LIBGL_ALWAYS_SOFTWARE=true prusa-slicer
) but this will make the preview render very slowly, making it hard to rotate around the object.Version
Version 2.3.0+linux-x64 (AppImage)
Operating system type + version
Arch Linux, up to date as of 2021-01-25 00:08Z
DE: KDE Plasma 5.20.5
WM: KWin 5.20.5 (X.org)
Clean installation of PrusaSlicer — removed both
~/.config/PrusaSlicer
and~/.PrusaSlicer
System Info
3D printer brand / version + firmware version (if known)
Original Prusa i3 MK3S+ (kit)
Behavior
Reproduction steps
Expected
Similar to 0.15mm, the preview first loads the plain yellow toolpath, then the "feature type" view replaces it
Actual
The preview displays the plain yellow toolpath, and then PrusaSlicer crashes, reporting a segmentation fault.
LOG FILE: prusaslicer-2.3.0-benchy-ultradetail.txt (obtained by
./PrusaSlicer-2.3.0+linux-x64-202101111322.AppImage --loglevel=9 | tee ~/prusaslicer-2.3.0-benchy-ultradetail.txt
)Notes
This does not appear to occur on simpler objects, even if they result in a vary large G-code file. This was confirmed by adding a 200 x 200 x 200 cube to the empty plate and slicing it at "0.15mm QUALITY". I tried slicing the same cube at "0.05mm ULTRADETAIL", but ran out of memory before it finished slicing.
Project File (.3MF) where problem occurs
Literally Benchy
The text was updated successfully, but these errors were encountered: