Skip to content
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

Slicer crashing with empty buildplate #5592

Closed
glstott opened this issue Dec 26, 2020 · 2 comments
Closed

Slicer crashing with empty buildplate #5592

glstott opened this issue Dec 26, 2020 · 2 comments

Comments

@glstott
Copy link

glstott commented Dec 26, 2020

Version

2.2.0+win64

Operating system type + version

Windows 10 Home version 1909

3D printer brand / version + firmware version (if known)

I have two and experience the issue with both. Prusa MK3S and a Monoprice Mini Delta. Up to date firmware on the former and a custom marlin on the latter. Neither are connected to my device during the crash.

Behavior

  • Application functions normally, allows me to work and set things up before crashing without any warning or notification and just disappearing.
  • I open the application. If this is my first time opening PrusaSlicer since restarting my PC, I operate as normal, and usually at some point in the process I hear a sound similar to the windows administrator privilege request sound. Then, it crashes and disappears (no consistency in what I'm doing at the time of the crash). After the first crash, each time I open it up, it crashes much more quickly such that the application becomes unusable. For example, while trying to get the version in the about page for this bug report.

Not a new feature request

Project File (.3MF) where problem occurs

No problematic files in particular. Usually I don't have anything on the build plate by the time it happens.

@lukasmatena
Copy link
Collaborator

Can you please test it with 2.3.0-rc2? it is quite possible that the issue will be no longer present.

If that version also crashes, could you run it from the command line with --loglevel=5 argument if that gives any clue? You can also try to run with --sw-renderer - if that helps, we will at least know that the problem is OpenGL related (did you try updating your drivers?). Some suspicious crashes were already reported on Win (#4316, #3374, #3177, #2939), this may be related.

@glstott
Copy link
Author

glstott commented Dec 27, 2020

Tested it with 2.3.0-rc2, and that resolved the problem. After one day of lots of active use on the slicer, no unexpected crashes. Thank you for the help!

@glstott glstott closed this as completed Dec 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants