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

Cura 11821 crash due to permission #2073

Merged
merged 5 commits into from
May 14, 2024

Conversation

saumyaj3
Copy link
Contributor

Description

writing debug.html in temp folder

writing debug.html in the current folder (in case of build the program data) makes it read only and no write modifications are allowed, hence crash. Now it is written in temp folder of the computer where writing the file is also allowed.
should solve : Ultimaker/Cura#18835

CURA-11821

saumyaj3 and others added 5 commits April 26, 2024 15:45
writing debug.html in the current folder (in case of build the program data) makes it read only and no write modifications are allowed, hence crash. Now it is written in temp foilder of the computer where writing the file is also allowed.
Also this code contains svg generation, which is majorly used in debugging application
Copy link
Member

@jellespijker jellespijker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@saumyaj3 I think the question you need to ask is why does it even tries to execute the code surrounded by the DEBUG guards, while the error happens on production.
It might be that this happens because the releases are now build with RelWithDebug, I'm not sure but you need to double check this, because now it feels like you are patching up a symptom and not the root-cause.

If it is indeed happening due to an added DEBUG preprocessor flag while building Cura for production. It could also explain this Sentry issue: https://ultimaker-o7.sentry.io/issues/5077178563/

@casperlamboo casperlamboo merged commit 8a3debd into main May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants