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
Git Master segfault using quickslice from gui #2801
Comments
Are you able to run Slic3r under valgrind? |
Hi alexrj ! |
Thank you for running under valgrind. This gives some hint but the bug is in Wx or in perl threading. I'll try to investigate. This is also related to #1636. |
I pushed a commit. Can you check whether it fixes the issue for you? Sadly, I can't reproduce the crash... |
@wolfmanjm reported this doesn't fix the issue for him. Can you try with the 1.2.6 binary package downloadable at http://slic3r.org/download ? I use perl 5.14 for those packages, and I wonder this might be a 5.18 issue. This would explain why I'm not able to reproduce it... |
Note to self, this is the relevant excerpt from @didli's valgrind output:
|
Strange : 1.2.6 binary is working, but only if i have NOT previously add an stl file on the plater tab. |
Sorry I am running perl 5, version 18, subversion 2 (v5.18.2) built for i686-linux-gnu-thread-multi-64int |
That valgrind report basically means that two concurrent Perl threads are free()ing the same Perl variables at the time of their destruction. This shouldn't happen because all Perl variables are automatically cloned when a thread is spawned. I wonder how to debug this further... |
My valgrind knowledge is quite close to 0 (-1 seems right too). Feel free to ask for any command you might think can help you. In the meantime, am i the only one reporting this issue ? Could it be a bad conf somewhere in my OS ? |
You're not the only one reporting this, but I'm afraid the bug lies somewhere outside Slic3r's code. Maybe it's inside perl itself, whose support for threads is not up to the job. The mid-term plan is to continue porting everything to C++/XS and do threading from there... |
This is probably fixed now, it just sliced for me (or it's not a bug in Slic3r at all and there's something dirty in your environment). http://dl.slic3r.org/dev for fresh builds Closing |
This seems to be duplicate of this one :
#2468
Trying to use quickslice feature from gui ends up in segfault (Fedora 21 x64). There's no issue for the same stl files using the command line. Perl is 5.18 (i think) in F21.
Here's a backtrace : http://didli.free.fr/Images/Forums/slic3r_backtrace.txt
STL file : http://didli.free.fr/Images/Forums/ramps_fan_40mm.stl
The text was updated successfully, but these errors were encountered: