Prusa Slicer terminates after import
Hi,
I started to use Prusa Slicer 2.3.3 after some time (previously used 2.3.0) and it is crashing after import of simple 3mf file.
Steps to reproduce:
1. Start Prusa Slicer 2.3.3
2. Import 3mf model
3. Click on tab "Simple" (or "Advanced" or "Expert")
Error messages I get are
1. Unhandled unknown exception, terminating the application. (click on OK button, the only one available)
2. Internal error: Calling AppConfig::save() from a worker thread! In Detail error is repeated twice. (Click on OK, the only button to continue)
3. Application terminates itself
Application Windows log under Event viewer does not show any info about crash.
Windows is Windows 10, Version 10.0.19043 Build 19043, running as guest inside Virtual Box. Host is Ubuntu 16.04.
Any idea what might be wrong here as this error is really annoying and Slicer unusable.
Regards
Darko
When trying to import file I get following error:
Best Answer by BogdanH:
After opening PrusaSlicer, add Shape-Box (right click on empty bed) and slice it. Then save the project (which will me 3mf file). Then close PrusaSlicer and open previously saved 3mf project. If it opens successfully, then there's something wrong with 3mf file which fails to open.. or PrusaSlicer just don't "like" that particular file 🙂
RE: Prusa Slicer terminates after import
After opening PrusaSlicer, add Shape-Box (right click on empty bed) and slice it. Then save the project (which will me 3mf file). Then close PrusaSlicer and open previously saved 3mf project. If it opens successfully, then there's something wrong with 3mf file which fails to open.. or PrusaSlicer just don't "like" that particular file 🙂
[Mini+] [MK3S+BEAR]
RE: Prusa Slicer terminates after impo
Many thanks for hint. I tried your case. On first occurrence I reproduced problem immediately with Shape-Box. But project was saved. Then a played a bit and moved project from nfs drive to local disk. And after some test Prusa Slicer started behaving correctly.
After that I couldn't reproduce problem either by importing same problematic model from local disk or nfs drive. So it became really strange. But it works, for now.
Having said all that: this was really strange behavior that I amt reproduce any ore.I'll reopen thread if I'll be bale to reproduce a problem at will.
So again, thanks for hint.
Thanks and regards
Darko
Cached?
You probably can't reproduce it because it's cached somewhere that PrusaSlicer likes.