Light burn software crashes when tracing images. There is no log message from light burn that I can find. The file I am working on also has no backup I can find.
I am using Big Sur v-11.3.1, 2.9gHz quad core i7, 16gb 2133 MHz lpddr3, 1536 hd graphics.
The terminal report:
The default interactive shell is now zsh.
To update your account to use zsh, please run chsh -s /bin/zsh.
For more details, please visit https://support.apple.com/kb/HT208050.
Ronalds-MacBook-Pro:~ ronaldgarner$ /Applications/LightBurn.app/Contents/MacOS/LightBurn ; exit;
2021-05-28 11:37:16.632 LightBurn[27687:778276] NSDocumentController Info.plist warning: The values of CFBundleTypeRole entries must be âEditorâ, âViewerâ, âNoneâ, or âShellâ.
QMetaObject::connectSlotsByName: No matching signal for on_actionEdit_Text_closed(int)
connected
âFaceTime HD Camera (Built-in)â â0x1420000005ac8600â
Port: 1452 5216
Port: 1452 4111
Port: 1452 4110
Port: 1452 5216
Port: 1452 4111
Port: 1452 4110
Execution of PAC script at âhttp://wpad/wpad.datâ failed: The operation couldnât be completed. (NSURLErrorDomain error -1003.)
I should add that I am drawing over the image, not using the image trace. Also, it is concerning that the auto save function is not working. It does not matter how long I work on the drawing, If I do not save it manually, there is no trace of the file once it crashesâŚ
I am getting a backup file recorded in the same folder as the original. The backup file is named using the "old_file_name" with "_backup" appended to the end of the file name. Are you not finding the same?
What do you have set for the âAuto-save Intervalâ in the âSettingsâ window (click âGearsâ icon to expose, then click âFile Settingsâ icon on left-side of that window)?
I ran a search for _backup, and the latest drawing to be backed up was a year ago. So, it was working and something changed a year ago⌠The plot thickens
This turned out to be a bug in the way that backups were sorted and managed - the system was sorting the backups by month / day / year, instead of year, then month, then day, so when the year rolled over it got confused and started deleting new backups. This is now fixed, and the fix will be in the next release.