Autoclose (crashing) when using post processing & trying to set up 'pause at height'

[BullseyeSBT 0]

When I try to use post processing > pause at height, the program instantly closes itself, can't seem to find anything on google some figured I would ask in here, this happens on both 5.7 & 5.8, it doesn't seem to do it on 3.2 but, 3.2 don't have the same 'pause at height' I want to pause at layer.

It crashes as soon as I change anything in the menu for pause at layer.

[Slashee_the_Cow 480]

I find this happens a lot if I have the "Automatic Slicing Toggle" plugin installed (and turned on). If I just click the pause button in the bottom right I can change post-processing script settings to my heart's content without it crashing (which is important if I'm trying to set up eight colour changes for the same project), then I can just turn it back on with the play button.

@ahoeben, even if that's not the OP's problem, any idea what's up with that?

 

If you're not using that plugin and you're having that problem, it might help us if you could upload the Cura log files. In Cura, go to Help > Show Configuration Folder (should open a file explorer window, just switch back to Cura for now) then make it crash by playing with post-processor settings. There should be a file named cura.log in the configuration folder and if you go to the folder above that there might be a file called stderr.log. If you can find those files and attach them to a post we can have a dig and see if there's any buried treasure.

[BullseyeSBT 0]

Thanks for the reply,

I would have shared the error log at the start.. but I didn't know where to find it.. tried google.. but you know google 🫠 🤣

Anyway the files you mention were exactly where you said they'd be 🥰

cura.log stderr.log

Edited November 7 by BullseyeSBT

[ahoeben 2,011]

1 hour ago, Slashee_the_Cow said:

I find this happens a lot if I have the "Automatic Slicing Toggle" plugin installed (and turned on).

Could you please try reproducing this with the Automatic Slicing Toggle plugin disabled, and with the "Slice automatically" option in the Cura Preferences turned on?

 

My plugin is mostly just a fancy button for that preference. But there could be an issue with updating the GUI in my plugin when the postprocessing plugin marks the project as needing a reslice.

[BullseyeSBT 0]

9 minutes ago, ahoeben said:

Could you please try reproducing this with the Automatic Slicing Toggle plugin disabled, and with the "Slice automatically" option in the Cura Preferences turned on?

 

My plugin is mostly just a fancy button for that preference. But there could be an issue with updating the GUI in my plugin when the postprocessing plugin marks the project as needing a reslice.

Well I just setup 'pause at height' with autoslice turned off, then sliced it manually, no crashes, so are we to assume it is a bug with autoslice?

[ahoeben 2,011]

@BullseyeSBT: It does not look like you have the "Automatic Slicing Toggle" plugin installed, so that mostly rules out my plugin a the culprit.

 

It seems there may be a bug caused by an interplay between the Post Processing plugin and the automatic slicing feature.

 

🎂

[BullseyeSBT 0]

4 hours ago, ahoeben said:

@BullseyeSBT: It does not look like you have the "Automatic Slicing Toggle" plugin installed, so that mostly rules out my plugin a the culprit.

 

It seems there may be a bug caused by an interplay between the Post Processing plugin and the automatic slicing feature.

 

🎂

Is this a bug that is likely to be fixed at some point?

[Slashee_the_Cow 480]

3 hours ago, BullseyeSBT said:

Is this a bug that is likely to be fixed at some point?

Do you have the "Slice automatically" setting that @ahoeben was talking about turned on?

Try turning it off if you do and see if that fixes it (and if it does, then install @ahoeben's plugin so you can change it easily 🙂

 

And if you don't have that turned on... then more thinking required 🤔

 

8 hours ago, ahoeben said:

My plugin is mostly just a fancy button for that preference. But there could be an issue with updating the GUI in my plugin when the postprocessing plugin marks the project as needing a reslice.

Thanks for pointing that out to my forgetful cow brain. I'll go complain to @GregValiant about how he manages to preferences for post-processing scripts that cause Cura to crash if automatic slicing is turned on.

[ahoeben 2,011]

@Slashee_the_Cow, I am still anxiously awaiting your feedback on whether the crash "that happens a lot" also happens without my plugin but with the "Slice automatically" option turned on.

[ahoeben 2,011]

11 hours ago, BullseyeSBT said:

Is this a bug that is likely to be fixed at some point?

Chances of this bug getting fixed are much higher if it gets reported in the proper channel.

https://github.com/Ultimaker/Cura/issues/

[GregValiant 1,409]

I've tried several combinations and with different plugins and post processors active.

• Sidebar GUI
• Tabbed Settings
• Advanced Fan Control
• Pause at Height
• Display Info On LCD

I attempted to force a crash with and without "Auto Slice Toggle" installed.  I enabled and disabled "Automatic Slicing".

 

With Auto Slicing enabled (and Auto Slice Toggle NOT installed):

I can occasionally force a crash by changing the settings in "Pause At Height" too quickly.  It's not consistent.  When it does crash, it crashes hard and Cura closes.

 

I'm going to guess that once in a while, depending where "Auto Slicing" is in it's progress, when a setting changes it can get hung up.  That change can be something as little as adding a second digit to a number in a setting box.

 

If the "Pause Layer" box has "25" in it and I want to change it to 431, then "Auto Slice" will start to run 4 times.

1. When I clear the layer box.
2. When I enter the "4"
3. When I enter the "3"
4. When I enter the "1".

That's actually the reason why I don't use "Auto Slicing".  There appears to be no latency when a value changes.  There should be an "are you done yet?" period of maybe 1/2 second to allow the user to finish typing before it jumps out and restarts.

[GregValiant 1,409]

FYI...Github report #19901 also describes this "crash because I type too fast" behavior.