-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Is there an existing issue for this problem?
- I have searched the existing issues
OrcaSlicer Version
2.3.1-dev 20e4f54
Operating System (OS)
Linux
OS Version
Debian trixie/sid
Additional system information
No response
Printer
n/a
How to reproduce
I've been debugging with gdb, had some crashes, filled up my disk with core files. I'm not sure which was the cause.
Another run logged:
[info] 2025-07-30 14:32:34.047479[Thread 0x00007fffe7da3540]:Failed to parse configuration file "/home/cory/.config/OrcaSlicer/OrcaSlicer.conf": [json.exception.parse_error.101] parse error at line 1, column 1: syntax error while parsing value - unexpected end of input; expected '[', '{', or a literal
Assuming a different run truncated or opened the file for write, but the disk was full.
Actual results
Config files shouldn't be overwritten; the new config should be written to a new file, the old config renamed, the new one renamed into place, then the old deleted (optional).
Expected results
The contents of OrcaSlicer.conf should never be completely lost.
Project file & Debug log uploads
debug_Wed_Jul_30_14_31_44_164422.log.0.txt
debug_Wed_Jul_30_14_32_34_164488.log.0.txt
Checklist of files to include
- Log file
- Project file
Anything else?
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working