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.

Sign up for GitHub

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

Jump to bottom

Cura crashes up to and including 3.03 #2644

Closed
jltott opened this issue Oct 20, 2017 · 35 comments
Closed

Cura crashes up to and including 3.03 #2644

jltott opened this issue Oct 20, 2017 · 35 comments
Labels
Status: Needs Info Needs more information before action can be taken.

Comments

@jltott
Copy link

jltott commented Oct 20, 2017

Have never been able to get this running. ALWAYS fails when you open a dialog box (save or open). Tried just about all releases on clean installs up to and including 3.03. Desperately want to try this but cannot. Windows 10 machine. Have requested help numerous times but never got any, one final time before I give up and ignore it forever...... Win 10 Home, Version 1703 OS build 15063.674 Intel I7@3.7GHz 16GB RAM
@chputney
Copy link

I installed Cura 3.03 to use all the new features on my Win7 machine. After installation, crash on opening. Finally uninstalled, deleted all cura appdata (why doesn't the uninstaller delete the appdata) and reinstalled. Now it opens, but crashes when I define a printer (Ultimaker original).

Stdout is empty.

Here is stderr.log:
stderr.log

Here is cura.log:
cura.log

@Vandrasc
Copy link
Contributor

Hi jltott,
Did you try to remove the AppData Cura folder? From both Roaming as Local?

chputney the AppData isn't automatically removed when uninstalling Cura by choice as some of the users still want to use their old configuration (printers, profiles etc.). Did you also remove the AppData from Local?

I can't reproduce the crash :( Maybe you could share with us your user directory before removing it? It may be something in your old configuration that causes the crash. Thank you!

@jltott
Copy link
Author

jltott commented Oct 21, 2017

Hi
Thought I had removed everything but in checking again I found I still had 2.7 as well as 3.03 AppData folders.
Saved them seperately, uninstalled 3.03 and deleted all appData folders referencing Cura
Reinstalled 3.03
Same problem, opened but crashed as soon as I tried to open a file
Here is stderr.log
stderr.log
cura.log is empty

Only files in user directory are machine files in .......\AppData\Local\cura\3.0\cache\definitions\3.0.3 the prusa i3 MK2 I am selecting appears to be the standard 324KB

All other/old Cura info now gone

Thanks

@jltott jltott closed this as completed Oct 21, 2017
@jltott jltott reopened this Oct 21, 2017
@jltott
Copy link
Author

jltott commented Oct 21, 2017

Sorry, wrong button

@jltott
Copy link
Author

jltott commented Oct 21, 2017

For info, if it is likely to help, the screen shots attached show sequence of failure since 2.3(?)
Cura screenshots.zip

@jltott
Copy link
Author

jltott commented Oct 21, 2017

Just to add confusion..... just installed MeshMixer. Guess what, it does exactly the same.

@chputney
Copy link

chputney commented Oct 22, 2017 •
edited

In trying to find a solution to Cura 3.03 crashing when adding a printer, I loaded Cura 15.04, Cura 2.4, and Cura 2.7. Using the same Win 7 machine with all these releases, I was able to add a printer.

Tried again with Cura 3.03. First uninstalled Cura 2.4, Cura 2.7 and Cura 3.03 using windows uninstaller and then deleted the directory appdata/Local/cura/3.0 and the directory appdata/Roaming/cura/3.0.

Reinstalled Cura 3.03 as administrator and accepted default installation options.

Cura starts with no problems and presents the "Add Printer" window. I select "Ultimaker Original" and click Add Printer.

Cura crashes after briefly flashing the next window.

Here are the logs:
cura.log
stderr.log

Looking at the logs, it seems that for some reason the printer data cannot be accessed.

There is nothing special about my Win7 machine. What could it be ?

@chputney
Copy link

chputney commented Oct 22, 2017 •
edited

Sometimes, the Add Printer gives a different error.

stderr.log

stderr.log

Ignore this, I was mistaken.

@nallath nallath mentioned this issue Oct 23, 2017
Closed
@fieldOfView
Copy link
Collaborator

I would not be surprised if this were caused by #2630

The shader that should draw the grid lines is broken on older GPUs. A fix was made, though it was not included in the 3.0 release. Some drivers draw the buildplate as a black plane, but it looks like some drivers may cause Cura to crash because of the broken shader.

You can fix this by replacing C:\Program Files\Cura 3.0\resources\shaders\grid.shader with this file:
https://raw.githubusercontent.com/Ultimaker/Cura/1313e01f04838ac0a2d83b332dc57b6f5db0b87c/resources/shaders/grid.shader

@chputney
Copy link

This was the solution. I replaced the file and was able to add a printer and start slicing.

Thank You !!!

@fieldOfView fieldOfView mentioned this issue Oct 23, 2017
Closed
@jltott
Copy link
Author

jltott commented Oct 23, 2017

Willing to try anything but sorry to be thick - how do I replace the file on my computer.

@fieldOfView
Copy link
Collaborator

  • Download the file (follow the link above, go to File -> Save Page As...)
  • In explorer, open the folder C:\Program Files\Cura 3.0\resources\shaders
  • Drop the file you downloaded into that folder
  • In the dialogs that pop up, allow overwriting the file

@jltott
Copy link
Author

jltott commented Oct 23, 2017

As I said, willing to try anything but as I thought, no solution. My problem is not one of choosing a machine but loading a file. Any other ideas anyone? By the way. Thank you anyway, I am glad it solved one persons problem.

@fieldOfView
Copy link
Collaborator

I am sorry, my solution was specifically for a 3.0 issue only, when drawing the buildplate for the first time. I had not noticed @chputney had taken the issue off topic...

@Ellecross
Copy link
Contributor

@jltott Hey your problem sounds familiar. I remember this problem was seen before with another user. Do you have happen to have Google Drive or Adobe Shell extensions?

Can you try removing them just to see if it will resolve your issue? Previously, this problem was seen happening with another user. He uninstalled either Google Drive or an Adobe extension (not sure which one caused it, but he uninstalled both) and after that, it worked for him.

@Ellecross Ellecross mentioned this issue Oct 26, 2017
Closed
@jltott
Copy link
Author

jltott commented Oct 26, 2017

Please keep open, thanks for the suggestions, I have to go into hospital for a week so will get back to this sometime after that. Thanks for all the help

@Ellecross
Copy link
Contributor

Ack! I hope all goes well @jltott <3

@ChrisTerBeke ChrisTerBeke added Type: Bug The code does not produce the intended behavior. Status: Fixed labels Mar 2, 2018
@Ghostkeeper Ghostkeeper added Status: Needs Info Needs more information before action can be taken. and removed Status: Fixed/Solved Type: Bug The code does not produce the intended behavior. labels Mar 26, 2018
@pegasis010
Copy link

I have this issue, no google drive or adobe other than adobe reader.
Cura 3.3.1 crashes on open or save dialog box.
Anyone else seeing this again?

@jltott
Copy link
Author

jltott commented Jun 3, 2018

Hi, for info I never got this working, certainly was never fixed, just moved on. deleted everything suggested, even deleted all Adobe references and files. Just gave up using (trying to) cura and meshmixer.

@pegasis010
Copy link

So in the off chance anyone other than jltott and myself are looking at this, the crash is happening when any windows file management dialogue box within Cura opens. Open, Save as, Export materials etc......

@jltott
Copy link
Author

jltott commented Jun 5, 2018

And if anyone does come up with a solution I would love to hear it.

@Ghostkeeper
Copy link
Collaborator

We haven't reproduced this issue ourselves here in the office but we've gotten reports about this from time to time. The problem back then was that some Windows extension (Adobe, Google) modified the file dialogue and this caused Qt to crash whenever Cura opened that file dialogue. You might still have some other modifications to the file dialogues, even ones that aren't very visible.

@jltott
Copy link
Author

jltott commented Jul 18, 2018 via email

@pegasis010
Copy link

pegasis010 commented Jul 18, 2018 via email

@jltott
Copy link
Author

jltott commented Jul 18, 2018 via email

@fieldOfView
Copy link
Collaborator

MeshMixer also uses Qt 5.8. Perhaps this will finally be fixed now that Cura is being upgraded to QT 5.10.

@jltott
Copy link
Author

jltott commented Jul 18, 2018 via email

@Ghostkeeper
Copy link
Collaborator

Qt is the software library that Cura uses to display its windows, buttons, etc.

@Ghostkeeper Ghostkeeper mentioned this issue Aug 13, 2018
Closed
@jltott
Copy link
Author

jltott commented Aug 13, 2018 via email •
edited by Ghostkeeper

@Ghostkeeper Ghostkeeper mentioned this issue Sep 3, 2018
Closed
@Ghostkeeper
Copy link
Collaborator

Can you try again using Cura 3.5?

@jltott
Copy link
Author

jltott commented Oct 12, 2018 via email

@jltott
Copy link
Author

jltott commented Oct 12, 2018 via email •
edited by Ghostkeeper

@jltott
Copy link
Author

jltott commented Oct 12, 2018

Still didnt work
stderr file as follows if it is of any interest
stderr.log

@Ghostkeeper
Copy link
Collaborator

This is suspected to be a duplicate of #1537. We can't confirm that yet since you said that disabling shell extensions didn't work, but that issue report might have some tips for you.

@pegasis010
Copy link

pegasis010 commented Oct 26, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: Needs Info Needs more information before action can be taken.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@fieldOfView @ChrisTerBeke @Ghostkeeper @jltott @Vandrasc @Ellecross @chputney @pegasis010