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.

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

Slicing failed #20363

Open
fiftystiff opened this issue Mar 8, 2025 · 10 comments
Open

Slicing failed #20363

fiftystiff opened this issue Mar 8, 2025 · 10 comments
Labels
Slicing Error 💥 A crash is caused by a model or a user interaction. This needs a differnt troubleshooting approach Type: Bug The code does not produce the intended behavior.

Comments

@fiftystiff
Copy link

Cura Version

5.9.1

Operating System

Windows 10

Printer

Ender 3

Name abnormal settings

Default, completely fresh install

Describe model location

No

Describe your model

Rectangular test box, but no models slice

Add your .zip here ⬇️

Box.zip

I have tried installing multiple versions and wiping every related file within AppData when uninstalling to do a completely clean install; nothing slices at all. I used to have no issues slicing and the first time slicing failed was right after I added a CR-10S. Since then slicing has never worked even after uninstalling/reinstalling multiple different versions.

@fiftystiff fiftystiff added Slicing Error 💥 A crash is caused by a model or a user interaction. This needs a differnt troubleshooting approach Status: Triage This ticket requires input from someone of the Cura team Type: Bug The code does not produce the intended behavior. labels Mar 8, 2025
@GregValiant GregValiant added Status: Needs Info Needs more information before action can be taken. and removed Status: Triage This ticket requires input from someone of the Cura team labels Mar 8, 2025
@GregValiant
Copy link
Collaborator

Thanks for the report.
The problem appears to be system specific. I didn't have any trouble slicing in 5.9.0 with a CR-10S active. (This is on a Windows 10 Pro laptop.)
After a failed slice, use the "Help | Export file for Technical Support" command and then go to the file, zip it, and post the zip folder. It will have the cura.log file in it. Maybe it will give a clue.

@fiftystiff
Copy link
Author

20x20x20 Cube Export.zip

File attached above is generated from the same machine as before, installed Cura 5.9.1; added CR-10S as printer, didn't change any print settings, slicing failed. I made a 20x20x20mm cube in Tinkercad to basically rule out the model as the problem.

I also just tried on another windows 10 PC that never has had any version of Cura installed; I downloaded/installed 5.9.1, launched, clicked through the setup stuff (without signing into Ultimaker account), added CR-10S when prompted, didn't change any settings or anything, drag/dropped file into Cura, and slicing failed.

@github-actions github-actions bot removed the Status: Needs Info Needs more information before action can be taken. label Mar 8, 2025
@fiftystiff
Copy link
Author

Another note to add: changing printer types still does not slice. I have an Ender 3 and a CR-10S, never had any issues until I added the CR-10S recently, but even when switching the printer to the Ender 3 slicing still always fails (no matter what model, including models that have previously sliced without issue).

@GregValiant
Copy link
Collaborator

I'm not having any trouble slicing it. I have about 20 printers installed of all sorts and checking with 5 or 6 they all slice the model.
We could use that log file.

@fiftystiff
Copy link
Author

I attached in my reply, is that the right thing? It was generated using the "Help | Export file for Technical Support" command you mentioned.

@GregValiant
Copy link
Collaborator

That's my bad. I opened it as a project.
From the log file is this line indicating a crash:
"Backend exited abnormally with return code 3221226505!"

I'm not familiar with that code. Someone from the Cura team will take a look.

@fiftystiff
Copy link
Author

I figured it out; I looked through the logs and it looks like the "Sentry" part was failing (see log below):

[MainThread] UM.Backend.Backend.startEngine [96]: Started engine process: C:\Program Files\UltiMaker Cura 5.9.1\CuraEngine.exe
[MainThread] UM.Backend.Backend._backendLog [140]: [Backend] Calling engine with: ['C:\Program Files\UltiMaker Cura 5.9.1\CuraEngine.exe', 'connect', '127.0.0.1:49675', '']
[EngineOutputThread] UM.Backend.Backend._backendLog [140]: [Backend] [2025-03-07 20:40:45.224] [info] Sentry url: https://[email protected]/4506257745510401
[EngineOutputThread] UM.Backend.Backend._backendLog [140]: [Backend] [2025-03-07 20:40:45.224] [info] Sentry config path: C:/s//AppData/Roaming/cura/.sentry-native
[EngineOutputThread] UM.Backend.Backend._backendLog [140]: [Backend] [2025-03-07 20:40:45.224] [info] Starting sentry
[EngineOutputThread] UM.Backend.Backend._backendLog [140]: [Backend] [2025-03-07 20:40:45.236] [info] Connecting to 127.0.0.1:49675
[EngineOutputThread] UM.Backend.Backend._backendLog [140]: [Backend] [2025-03-07 20:40:45.237] [error] Could not connect to the given address
[EngineOutputThread] UM.Backend.Backend._backendLog [140]: [Backend] [2025-03-07 20:40:45.350] [info] Closing sentry
[EngineOutputThread] UM.Backend.Backend._backendLog [140]: [Backend] [2025-03-07 20:40:45.443] [info] Closing connection.
[MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:\Program Files\UltiMaker Cura 5.9.1\share\uranium\resources\shaders\toolhandle.shader]...
[MainThread] CuraEngineBackend.CuraEngineBackend._onBackendQuit [1065]: Backend exited abnormally with return code 3221226505!

I disabled my VPN and it worked immediately, then re-enabled the VPN and slicing failed; then I disconnected my network cable and slicing succeeded, so it's probably a bug with the VPN not allowing connection to "Sentry" and Cura getting hung up on that rather than just recognizing that it can't connect.

@fiftystiff
Copy link
Author

I also checked on my VPN settings; I have split tunnel enabled and Cura is not on the list of programs that should be running through the VPN, so I am not sure if that is a bug with split tunnel with my VPN or a bug with Cura.

@GregValiant
Copy link
Collaborator

You can try going to "Preferences" and the "General" tab and scrolling to the bottom. Turn off the "Privacy" and "Update" options. With those off, I would think that Cura wouldn't try to access a network.

@fiftystiff
Copy link
Author

That still failed:

  • I ran a slice with my VPN disabled (succeeded)
  • I enabled my VPN and ran a slice (failed)
  • I disabled all options in the "Privacy" and "Updates" sections and ran a slice (failed)
    Image

-I updated my VPN to the latest (slightly newer) version and ran a slice with VPN enabled (failed)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Slicing Error 💥 A crash is caused by a model or a user interaction. This needs a differnt troubleshooting approach Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

2 participants