Notifications
Clear all

Prusa Slicer Crashing  

Page 5 / 5
  RSS
Neophyl
(@neophyl)
Illustrious Member
RE: Prusa Slicer Crashing

Well your project slices on my windows pc.  It takes awhile to generate the gcode (around 5 minutes) and then it seems to pause and be non responsive for about another 3-5 minutes while it generates the preview layers/colour coded preview.  It doesn't actually crash my pc though.

I will say that the choice of gyroid for infill is one of the worst you could make for large models.  It uses way more memory and its bigger too as the infill is constantly changing direction.  Using Cubic works out much much quicker to process and the infill is just as strong as gyroid.  Basically unless it for aesthetic reasons I avoid gyroid.

Also you have Avoid Cross perimeters enabled which is apparently very memory intensive.  On something like this that asking to slow things way down.

Also I hope you weren't planning on printing the project like that if you could slice it ?  It would result in one big mess of plastic.  Parts are not orientated in the best angles for printing and there is zero support.  Its just asking for a Blob of doom.

I do think PS has some form of memory issue though, as even now its sliced it stutters when I try and rotate the sliced preview, its jerky in response to mouse movements.  I mean I don't have the fastest machine but even so its was new last year and it doesn't have these issues with other software.  It should be able to rotate the preview around.  Glad I dont have a bed size that big (300x300 is my max).

Posted : 30/01/2021 9:07 pm
Neophyl
(@neophyl)
Illustrious Member
RE: Prusa Slicer Crashing

(Ran out of edit time)

See if this project will slice for you ?

Attachment removed
Posted : 30/01/2021 9:20 pm
karl-herbert
(@karl-herbert)
Illustrious Member
RE: Prusa Slicer Crashing

@neophyl

I installed the latest PS 2.3.0 and ran your .3mf.

Calculation time approx. 1 minute 50 seconds. Here the gcode:

snorklewhycrash_neo.zip

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.

Posted : 31/01/2021 12:13 am
MasterCATZ
(@mastercatz)
Active Member
RE: Prusa Slicer Crashing

gave it some thought and decided to remove amdgpu.dcfeaturemask=2 amdgpu.ppfeaturemask=0xffffffff from my kernel parameters

(allowed memory down clocking with multi displays) it seems something must be going wrong with the slicer when the memory is idling under 100mhz

 

now instead of GPU crashing the slicing program just segfaults

 

attached log  

[2021-01-31 10:58:08.676337] [0x00007fdabc7e25c0] [error] OpenGL error in ../src/slic3r/GUI/GCodeViewer.cpp:1894, function refresh_render_paths() : 1281 - Invalid Value

 

 

 

Attachment removed
This post was modified 3 years ago 4 times by MasterCATZ
Posted : 31/01/2021 12:59 am
Neophyl
(@neophyl)
Illustrious Member
RE: Prusa Slicer Crashing

@mastercatz

You need to post any errors to the github site really.  I know there are a few currently active for linux systems and segfaults.

@karl-herbert I was interested to see if @mastercatz could slice it successfully on his system with the changed infill type to cubic rather than gyroid and with avoid cross perimeters off .  On mine is generates it in a little over a minute too but seeing as mine doesn't have an issue at the moment and will slice it with gyroid (even if slow) its not very useful.

Posted : 31/01/2021 1:13 am
MasterCATZ
(@mastercatz)
Active Member
RE: Prusa Slicer Crashing

@neophyl

 

same issue with your settings 

 

it is more of a quick part dump on plate to work out how many metres it was going to use 

 

looks like I will have to use virtualbox for slicing for now 

 

 

Posted : 31/01/2021 2:03 am
Marlon B
(@marlon-b)
Member
RE: Prusa Slicer Crashing

All I  did was Disable Nvida Drivers in Device Manager then tried opening PursaSlicer again.

It again crashed PursaSlicer after I did this.

Then I re-enabled the Nvida drivers in Device Manager, opened PursaSlicer and this time everything worked perfectly. Driver Glitch maybe? 

Posted : 31/12/2023 2:33 am
Page 5 / 5
Share: