PrusaSlicer crash on drop down menu
 
Notifications
Clear all

PrusaSlicer crash on drop down menu  

  RSS
kzr
 kzr
(@kzr)
New Member
PrusaSlicer crash on drop down menu

Any of you have experienced that a newly installed PS will crash as soon as any kind of drop down is clicked?
It happens when clicking anything on the menu bar, changing print settings/filament/printer in the right corner or even left clicking the top bar.

Its a new win 10 pro, with a Quadro p2200 card.

Posted : 13/09/2021 3:40 pm
cwbullet
(@cwbullet)
Member
Version

Which version of PrusaSlicer?

--------------------
Chuck H
3D Printer Review Blog

Posted : 14/09/2021 10:17 am
kzr
 kzr
(@kzr)
New Member
Topic starter answered:
Re: Version

2.3.3, have just installed it on a clean Win10 pro.

Posted : 14/09/2021 11:02 am
BogdanH
(@bogdanh)
Honorable Member

No crashes here with PS 2.3.3 on Win10 Pro 64bit.

[Mini+] [MK3S+BEAR]

Posted : 14/09/2021 2:04 pm
towlerg
(@towlerg)
Noble Member

Obviously I don't know if this applies to you but several users have reported similar problems with high end video cards. Perhaps you could do driver upgrade? Also look in crash logs, you may be able to identify the driver with a problem.

Posted : 15/09/2021 11:36 am
Kodachrome
(@kodachrome)
Active Member
RE: PrusaSlicer crash on drop down menu

Has anyone else seen this? I know this thread is a year old, but this is exactly whats happened to me. It was fine, everything works if I dont click any profile or drop down menu at all.

 

Ive tried everything from 2.5 RC2 back to the release version of 2.4, no change at all. Win 11 Pro , RTX 3090.

Posted : 01/09/2022 8:51 am
Kodachrome
(@kodachrome)
Active Member
RE: PrusaSlicer crash on drop down menu

Seems its a thing found  by others at the moment, also with Win11 Insider: https://github.com/prusa3d/PrusaSlicer/issues/8641

 

Posted : 01/09/2022 9:11 am
Neophyl
(@neophyl)
Illustrious Member
RE: PrusaSlicer crash on drop down menu

One question, what mode are you in ? (Simple/Advanced/Expert).  There was an issue that only showed up if you were in simple mode, but wasn't directly related to that, it was just repeatable if you were in that mode.

Also you could start with the log level switch ( --loglevel=9    ) and see what the logs generate.  Then open an issue on github once you have all the required info to open an issue.

Posted : 01/09/2022 9:18 am
Kodachrome
(@kodachrome)
Active Member
RE: PrusaSlicer crash on drop down menu

Expert mode. 

 

Ive done the log level thing.. But where are the log files? Looking at the verbose output in the command line.. It just stopped updating the terminal window when it locks up. 

Posted : 01/09/2022 9:42 am
Neophyl
(@neophyl)
Illustrious Member
RE: PrusaSlicer crash on drop down menu

you have to use the prusa-slicer-console.exe --loglevel=9 (or whatever level).  That way it logs it to the console window.  I dont know which level is needed for your issue though, only the devs could tell you that.  I think 9 just logs everything it can though.

Posted : 01/09/2022 9:50 am
towlerg
(@towlerg)
Noble Member
RE: PrusaSlicer crash on drop down menu

This may be a red herring but some problems on installations where GPU is used seem to be solved by using software rendering (also worth checking that divers are up to date).

Posted : 01/09/2022 12:29 pm
kzr
 kzr
(@kzr)
New Member
Topic starter answered:
RE: PrusaSlicer crash on drop down menu

I found out that my problem was a DLL injecting program that messed it up.

Posted : 08/09/2022 8:42 am
Neophyl
(@neophyl)
Illustrious Member
RE: PrusaSlicer crash on drop down menu

Thanks for reporting back what the issue was.  At least now if someone in the future can find this post again they can see if they have the same thing.

 

Posted : 08/09/2022 9:46 am
Kodachrome
(@kodachrome)
Active Member
RE: PrusaSlicer crash on drop down menu

Wait wait hold on a sec @kzr ... what DLL injecting program? My issue (and Ive seen others report this too, on this issue) literally just went away the next day with no change. Ive since reinstalled Windows for other reasons (though same hardware and drivers) and currently do not have the issue.  I dont think a vague "DLL injection" has clarified what the issue was/is at all!? 

Posted : 08/09/2022 9:52 am
Share: