Cura freezing on setting/profile changes

[Wcj97 0]

     I've had an issue with Cura freezing for a while. It used to happen every once in awhile when changing print settings. I disabled auto-slice and that fixed the issue for awhile. Now, recently, I've started trying to use Cura to slice for my custom FDM printer, but the issues is back. Now Cura freezes any time I attempt to make setting changes to the printer profile in 'Manage Printers'. This is becoming incredibly frustrating because it's preventing me from using Cura as a slicer for my new printer.

     I bit ago I read that there is a bug in the grid.shader file that can cause this issue, and someone suggested replacing that file with a different one from GitHub. Others (having fairly similar problems) said this worked for them, but I was not able to replace the file (something about not having permission from the owner to make changes).

     Is anyone else having this issue? Can anyone help me find a way to resolve the problem?

 

Thanks!

[Wcj97 0]

Also, in case this helps a diagnosis, Cura has been freezing when saving a gcode file for my new printer profile. It seems to slice fine, and actually saves all of the print gcode, but freezes towards the end of the save so that my gcode file does not have my 'end gcode' written. This means when my printer finishes the print, it does not lift the z, or home, or even shut off the hot end - it just stops right where it read the last line of gcode in the file. Seriously this is all becoming super frustrating.

[ahoeben 1,948]

The grid shader bug never had anything to do with settings or writing gcode. You seem to have uncovered a new bug that I at least have not seen reported before (especially the gcode bit)

[Wcj97 0]

Just now, ahoeben said:

The grid shader bug never had anything to do with settings or writing gcode. You seem to have uncovered a new bug that I at least have not seen reported before (especially the gcode bit)

Is there a way for me to post a log of Cura for someone to take a look at? I've seen others do that in similar discussions, but I'm not totally sure how to pull the logs

[ahoeben 1,948]

In Cura, go to Help -> Show configuration folder.

The folder that opens should have a Cura.log file in it. It is probably large, too large to attach here. So please upload it on some cloud storage platform and post a link.

 

Note that I am not an Ultimaker employee, I just contribute to the Cura project. The best way to get the developers attention is to post an issue here: http://github.com/ultimaker/cura/issues