https://bugzilla.redhat.com/show_bug.cgi?id=1046006
Bug ID: 1046006 Summary: Slicing a .stl file fails if multiple threads are configured Product: Fedora Version: 20 Component: slic3r Severity: high Assignee: mhroncok@redhat.com Reporter: neil@darlow.co.uk QA Contact: extras-qa@fedoraproject.org CC: mhroncok@redhat.com, perl-devel@lists.fedoraproject.org
Description of problem: If 2 (the default) or higher is selected in Print Settings|Advanced|Threads an error is reported and slicing fails.
Version-Release number of selected component (if applicable): slic3r-1.0.0-0.2.RC1.fc20.x86_64
How reproducible: Every time
Steps to Reproduce: 1. Attempt to slice a .stl file with default settings 2. Observe error and slicing failure
Actual results: Can't locate package GLUquadricObjPtr for @OpenGL::Quad::ISA at /usr/share/perl5/vendor_perl/Slic3r.pm line 111.
Expected results: Slicing should be performed without error.
Additional info: Reducing the Threads value to 1 permits slicing to be performed. I have reported this upstream as Issue #1636 at https://github.com/alexrj/Slic3r
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
Miro Hrončok mhroncok@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED
--- Comment #1 from Miro Hrončok mhroncok@redhat.com --- I cannot reproduce the issue. Maybe it's some package I have installed and you don't (and that is missed as a Require). I'm trying to reproduce this in virtual environment.
Thanks for reporting this upstream.
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #2 from Miro Hrončok mhroncok@redhat.com --- Oh, are you using Quick slice from file menu? I can reproduce it then.
This should fix it: https://github.com/alexrj/Slic3r/commit/5470fbbebc1d4ae5eb09196fd2c36ff3515d...
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #3 from Miro Hrončok mhroncok@redhat.com --- Here is a scratch build of slic3r 1.0.0RC.
http://koji.fedoraproject.org/koji/taskinfo?taskID=6353379
Could you please test, if it crashes for you too, when doing a quick slice with 2+ threads?
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #4 from Miro Hrončok mhroncok@redhat.com --- I meant slic3r 1.0.0RC2.
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #5 from Neil Darlow neil@darlow.co.uk --- ABRT was invoked and reported that Perl had caught a SIGABRT.
This was with 2 threads selected and reducing threads to 1 allows Quick Slice and Save As... to work correctly.
This is proving to be quite a puzzle.
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #6 from Miro Hrončok mhroncok@redhat.com --- Thanks for testing it.
In the meantime, as a workaround, I recommend you either add the STL to the plater and use Export GCODE button, or if you want to be really quick, use command line interface to slice a single STL file.
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #7 from Neil Darlow neil@darlow.co.uk --- My desktop is a 3.3GHz 64-bit dual-core machine. I can live with just one thread for now.
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #8 from Miro Hrončok mhroncok@redhat.com --- slic3r 1.0.0RC3 http://koji.fedoraproject.org/koji/taskinfo?taskID=6603224
Still crashes. I think this might be in wxPerl somewhere :(
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
Miro Hrončok mhroncok@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |julien.boucaron@gmail.com
--- Comment #9 from Miro Hrončok mhroncok@redhat.com --- *** Bug 1123638 has been marked as a duplicate of this bug. ***
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
Miro Hrončok mhroncok@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Slicing a .stl file fails |Slic3r crashes on Quick |if multiple threads are |Slice if multiple threads |configured |are configured
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
Miro Hrončok mhroncok@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |neil@darlow.co.uk Flags| |needinfo?(neil@darlow.co.uk | |)
--- Comment #10 from Miro Hrončok mhroncok@redhat.com --- Slic3r 1.1.7 seems to remove thread option. Quick slice works.
You can test it on F21, slic3r 1.1.7 is pending to testing.
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
Neil Darlow neil@darlow.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(neil@darlow.co.uk | |) |
--- Comment #11 from Neil Darlow neil@darlow.co.uk --- I do not have F21 but I have Slic3r-1.1.7 installed from tarball on F20.
The Threads option is still there for me under Print Settings|Advanced at the bottom of the dialog.
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #12 from Miro Hrončok mhroncok@redhat.com --- Created attachment 940992 --> https://bugzilla.redhat.com/attachment.cgi?id=940992&action=edit Fedora 21 slic3r 1.1.7 screenshot
This is what I see in F21. But running from binary tarball displays that option, as you say. Weird. Maybe a missing dependency.
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #13 from Miro Hrončok mhroncok@redhat.com --- Nevertheless it solves the problem, right?
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #14 from Miro Hrončok mhroncok@redhat.com --- lib/Slic3r.pm: $have_threads = $Config{useithreads} && eval "use threads; use threads::shared; use Thread::Queue; 1";
I'll check these.
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #15 from Neil Darlow neil@darlow.co.uk --- That is a pretty big clue to what is happening.
Slic3r-1.1.7 from tarball *does not* exhibit this bug but we cannot exclude a packaging problem.
I am no Perl expert but:
&& eval "use threads; use threads::shared; use Thread::Queue; 1";
looks suspicious.
It obviously checks for various threading modules and the "1" is presumably for when none is detected but does it act as if something has been detected? I am wondering if that should actually be "0"?
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #16 from Miro Hrončok mhroncok@redhat.com --- 1 will be evaluated only if all of those modules are loaded without error
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #17 from Miro Hrončok mhroncok@redhat.com --- Thread::Queue it is, when installed, it adds the option. And the crash is still there :(
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #18 from Miro Hrončok mhroncok@redhat.com --- *** Bug 1146704 has been marked as a duplicate of this bug. ***
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
Miro Hrončok mhroncok@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bugzilla77@free.fr
--- Comment #19 from Miro Hrončok mhroncok@redhat.com --- *** Bug 1177679 has been marked as a duplicate of this bug. ***
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #20 from Fedora End Of Life endoflife@fedoraproject.org --- This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
Fedora End Of Life endoflife@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution|--- |EOL Last Closed| |2015-06-29 20:47:53
--- Comment #21 from Fedora End Of Life endoflife@fedoraproject.org --- Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
Miro Hrončok mhroncok@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |NEW Version|20 |21 Resolution|EOL |--- Keywords| |Reopened
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #22 from Fedora End Of Life endoflife@fedoraproject.org --- This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
Fedora End Of Life honza.kurik@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |WONTFIX Last Closed|2015-06-29 20:47:53 |2015-12-01 22:05:09
https://bugzilla.redhat.com/show_bug.cgi?id=1046006
--- Comment #23 from Fedora End Of Life honza.kurik@gmail.com --- Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
perl-devel@lists.fedoraproject.org