Slicer version 2.3 causing full system crash
Hello,
First off, why does hitting the "report an issue" in the help tab for the slicer take you to GitHub? That's not a place to report bugs, crashes, or overall issues with software. If your team wants to collaborate on that site then leave that to an internal work group. Give customers a straight forward spot to make reports. It could even be an email for reports that is suggested. I am not going to use GitHub to find a forum location that might be the best spot to make a report as a customer of your product. A forum post is not a spot to make software issue reports.
The Problem:
I am having a full system crash that requires a full reboot when I am loading my build plate on the prusaslicer version 2.3 and I hit "slice". This has happened twice since I update my software. I have noticed that I have more than 6 items on the build plate. Once was with items that didn't need supports added and once when supports were needed. I am using 0.10mm detail, with 15% infill, generic PLA, on the i3 MK3 settings. They have all been simple figures for a D&D game. I do not get any reportable error codes after rebooting the system and restarting the program. Windows error screen states a report is being made for Microsoft. Unfortunately the issue seems to rest inside the code for the prusaslicer version 2.3.
RE: Slicer version 2.3 causing full system crash
First of all Github is not a forum. This is a forum. Yet you posted here anyway after saying you wouldn't use a forum. This is NOT the correct place to report issues as it is a user to user forum too. The Devs DO use Github though as that is the place Prusa as a company has decided to do it. They are not the only company to do so either. It is the chosen and correct place to report all issues. Github is a code repository and an issue tracking system.
If you do not wish to use the system provided then that is up to you. All issues created there get a proper tracked issue number and can be monitored by the Prusa team. Anything posted here might get you some help but might not too if no one else has had the same issues.
Regardless of what you decide to do there are certain basic information required when reporting any issue. First is a copy of the project that is causing you issues. In Prusa Slicers case that would be the saved project .3mf file. Any files posted either here or on github will require zipping into an archive to be accepted as the file types allowed are quite restricted. Secondly for your case your system specifications, memory, driver versions etc would also be very helpful.
Its why there is an issue reporting template on github for you to fill in so that you don't miss basic required information. If the devs cant duplicate the issue then there is little chance that they will be able to do anything about it.
If you had posted on github then they would likely have asked you to try it while starting PS with various log level switches enabled. Usually "prusa-slicer-console.exe --sw-renderer --loglevel=5" on a windows based machine. This generates extra logging. Please don't post the results here though as we aren't Prusa developers. Post it on Github. Where it belongs.
RE: Slicer version 2.3 causing full system crash
FWIW this forum is a user to user board and is not actively monitored by Prusa staff. I was under the impression that part of githubs function was to centralized issue reports on open source software.
In the past I've been accused of being a PrusaSlicer apologist because I suggested workarounds or pointed out thats just how it works. The number of people reporting problems with 2.3 is tiny. That said most of the problems posted fall into three categories, video drivers, Mac OS and complex pointing devices. You obviously aren't running a Mac so perhaps you could post your OS version, Video and drivers. I'm genuinely trying to help but if you are unhappy with that then ignore this post.
RE: Slicer version 2.3 causing full system crash
@neophyl
people like you are why I don't like posting on forums. The forums of either the actual prusa site or github are the only place I had to choose to make any kind of report. I chose the actual prusa site. I will not intrude on your territory ever again with my ridiculous notions of wanting a straight forward reporting system for bugs and errors. So sorry to anger the Great and Wonderous Noble Member that you are. thanks for reinforcing the idea that forums are for TROLLS and the small amount of info on github. Who is sending me emails after having to create a profile ,just to report a bug, to have me update my profile and add any new projects just like forums do.
RE: Slicer version 2.3 causing full system crash
@towlerg
Thanks for actually making a reasonable post that is helpful. If GitHub is meant to be a centralized way to compile reports. Then it does it in a round about adventure style of doing it. The system I am using is Windows 10 with with a I7 4790k cpu, and an older GTX 750 video card. I have recently update the drivers. But who knows there may be something that needs to be adjusted or updated on that end. just hadn't noticed any issues with the prusa slicer until the update to 2.3. The crash does happen as the slicer is rendering the image for details on the build. It could easily be a video rendering computation that overwhelms the system causing the crash. I'll play with it. Thanks again for the information.
RE: Slicer version 2.3 causing full system crash
BTW I forgot to ask, is it one particular .STL that causes Prusaslicer to crash, if so perhaps you could post it and I'll see what happens on mine.
I wonder if your motherboard has onboard video, if so you could try using that to eliminate GTX drivers. Also did you upgrade the video drivers before or after you experienced PrusaSlicer 2.3 crash? If before perhaps you could reinstate previous version.
Just one more thing, when 2.3 was first released the install was incorrect (presumably it was compiled like alpha and beta without proper install program) that was quickly replaced by a proper install. Perhaps it might be worth your while redownloading and reinstalling just to certain you have a good image.