Bug 1046006
| Summary: | Slic3r crashes on Quick Slice if multiple threads are configured | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Neil Darlow <neil> | ||||
| Component: | slic3r | Assignee: | Miro Hrončok <mhroncok> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 21 | CC: | bugzilla77, julien.boucaron, mhroncok, neil, perl-devel | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-12-02 03:05:09 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Neil Darlow
2013-12-23 07:48:49 UTC
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. Oh, are you using Quick slice from file menu? I can reproduce it then. This should fix it: https://github.com/alexrj/Slic3r/commit/5470fbbebc1d4ae5eb09196fd2c36ff3515d5b6c 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? I meant slic3r 1.0.0RC2. 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. 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. My desktop is a 3.3GHz 64-bit dual-core machine. I can live with just one thread for now. slic3r 1.0.0RC3 http://koji.fedoraproject.org/koji/taskinfo?taskID=6603224 Still crashes. I think this might be in wxPerl somewhere :( *** Bug 1123638 has been marked as a duplicate of this bug. *** 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. 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. Created attachment 940992 [details]
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.
Nevertheless it solves the problem, right? lib/Slic3r.pm: $have_threads = $Config{useithreads} && eval "use threads; use threads::shared; use Thread::Queue; 1";
I'll check these.
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"? 1 will be evaluated only if all of those modules are loaded without error Thread::Queue it is, when installed, it adds the option. And the crash is still there :( *** Bug 1146704 has been marked as a duplicate of this bug. *** *** Bug 1177679 has been marked as a duplicate of this bug. *** 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. 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. 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. 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. |