-
-
Notifications
You must be signed in to change notification settings - Fork 520
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
Segfault when changing to preview #1057
Comments
not much, sadly most of the interesting stuff is behind the |
I tried compiling with debug symbols, but the function names are still not visible for some reason:
The way I tried to enable the symbols was changing CMAKE_BUILD_TYPE to Debug in the package's build script.
Am I doing it correctly? |
I'm affected by this on Arch as well, had to downgrade to the previous version for now. |
I'm sorry, but I never had to build on debug on linux, so I don't know that much. @lordofhyphens Do you know how to debug in Linux? |
@gkatev did you execute the binary that is installed by the package or did you execute the binary in the source tree? If it's the later, the missing debug symbols are explained by the fact that makepkg strips all ELFs and SO of them during the packaging process. |
There is a documentation on how to not strip debug symbols here: https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces I'll see if i can try to get a proper stacktrace. |
Does this help?
|
Ah, good to know, thanks. I was able to get a backtrace with symbols. It does seems quite different from @codingcatgirl's one though.
|
That is definitely wild and yes, very different. I absolutely can't rule out i did something wrong, c++ isn't my native language, so to speak :D |
There's a separate assert() that I've been able to trigger when selecting the GCode View w/o having anything on the plate. |
On this branch over at slic3r/Slic3r: https://github.com/slic3r/Slic3r/tree/merill-merge I've tweaked some of the build items so that if you supply
|
FYI there are a bunch of similar-looking issues on the PrusaSlicer repo; prusa3d#6342, prusa3d#5889 to name some. Somewhere I saw a suggestion of launching with LIBGL_ALWAYS_SOFTWARE=true, which does work for me. The preview is quite laggish with it, but at least it doesn't crash.. |
can you test the latest version? |
@supermerill By latest, you mean 2.3.56.1 or git master? Edit: Actually, both of these versions give me an assertion fail when switching to the sliced preview (with an object in the plater), like in #1056. |
I tried the Nightly branch and I'd say the issue seems to have been resolved. On prusa3d#5889 it's been noted that the behaviour is also dependent on the particular model and its comlexity (in some regard). I don't know to what degree the underlying cause has been fixed or if my success is circumstantial, but I tried a couple different models (somewhat computationally-intensive to slice ones), and Superslicer didn't crash! |
nice! |
I'm not sure, I think I'm on the old layout (sliced preview is on the bottom-left). The Nightly branch is the only one I've tested, since others would give me an assertion error (#1056). |
Version
Version 2.3.55 (AUR's superslicer 2.3.55.5-3)
Operating system type + version
Arch Linux
Behavior
Hi,
Superslicer is crashing on me, with some STLs (not with others), when switching to preview.
(So to be clear, import STL; all good. As soon as a I click to view the printing preview; crash)
G-Code generation still works correctly.
All I really have to offer as a symptom is the coredump, which does not seem all that useful tbh, but maybe someone else might be able to reproduce or chime in.
It seems to be a wxgtk issue, but also, it does not occur in superslicer 2.2.54.2.
Furthermore, it also occurs in Prusaslicer 2.3.0 (Arch's prusa-slicer 2.3.0-1), and on super/prusa's g-code viewer.
Note that superslicer uses wxgtk 3.1.4, whereas prusaslicer wxgtk 3.0.5.1.
Prusaslicer's backtrace:
Project File (.3MF) where problem occurs
Crashes: MainBody_175mm_6mm_Fitting_Captive.zip
Does not crash: Brace_Back.zip
Hope there's enough to go off on, let me know if and how I could help.
The text was updated successfully, but these errors were encountered: