Lightburn crashing unexpected error on MacOS

I’ve been using LB on my M1 mac for some time, no issues. I design on the M1 and have a dedicated windows system I use for burning.

Starting today (no system changes that I’m aware of) LB fails to start with an unexpected error. Looks to be something with the runtime library? I’ve pasted the crash log below. I have uninstalled and re-installed LB, same error. Any pointers would be appreciated.


Translated Report (Full Report Below)

Incident Identifier: 12DA9992-6D1E-4B3A-BC6B-3E292D6F89D4
CrashReporter Key: 2D1827A7-45E6-7552-BADC-AA5BE67F434B
Hardware Model: MacBookPro18,3
Process: LightBurn [2170]
Path: /Applications/LightBurn.app/Contents/MacOS/LightBurn
Identifier: com.LightBurnSoftware.LightBurn
Version: ???
Code Type: X86-64 (Native)
Role: Background
Parent Process: launchd [1]
Coalition: com.LightBurnSoftware.LightBurn [1599]

Date/Time: 2022-04-24 14:59:25.4169 -0500
Launch Time: 2022-04-24 14:59:19.6239 -0500
OS Version: macOS 12.0.1 (21A559)
Release Type: User
Report Version: 104

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x00007ff7ffd6faf8
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: SIGNAL 5 Trace/BPT trap: 5
Terminating Process: exc handler [2170]

Triggered by Thread: 0

Application Specific Information:
assertion failed [header->version <= kProjectSourceVersion]: runtime library is newer than runtime
(Library.cpp:99 init)

Anyone out there that can help? I have been unable to resolve this issue after uninstalling and re-installing. Very frustrating. Throws exception immediately upon trying to open the app. Ran fine for weeks.

Thank you for bringing this to our attention. Which version of LightBurn are you running? We released a patch within the last day or so.

Please try that and update us when you can. :slight_smile:

This is most likely an issue with Rosetta.

Try reinstalling Rosetta.

See here for more information:
Fix Apps Crashing on M1 Pro/Max Mac After Migration Assistant or Monterey Update (osxdaily.com)

Thanks for the responses. I updated to the 1.1.04 release and had the same issue. Was going to try the rosetta reinstall as Berainlb suggested but did a macOS update first. That fixed the issue. Probably reinstalled rosetta as part of that is my guess. FYI… I’m on MacOS 12.3.1 Thanks again!

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.