Lightroom Classic quit unexpectedly.

[cephotographyuk]

Error messge is 'Lightroom Classic quit unexpectedly'.

I get the message when quitting Lightroom.

Running Lightroom 14.1.1 on Mac OS 13.7.2 (22H313) Ventura.

Issue only started after updating to the latest release of Lightroom Classic.

Any suggestions?

Thank you!

[cephotographyuk]

And it didn't last long sadly. The error has returned which is now proving to be intermittent. @Sameer K are you getting these messages?

[roberts77626518]

Adobe closed my case and told me to upgrade to 14.2. I am getting the same error unless I uncheck optimize. I've unchecked both and get the error too. So for now, I uncheck optimize and optimize the catalog after I start Lightroom.

I've been unable to contact Adobe to reopen my case to date. Maybe tomorrow.

[LarryLarz]

I too, just started to have this crash, which occurs right before (or perhaps instantly after) I back up my Lightroom Classic catalog. I have a 2017 iMac 27 inch running the latest Ventura version 13.7.4.  I didn't have this problem until I updated Lightroom to version 14.2.  I can still open Lightroom and everything seems to be in order, but this does not inspire confidence.  I have sent multiple crash reports to Adobe.    Adobe please fix this known issure. Thanks.

[roberts77626518 · Accepted solution]

Just updated to Ventura 13.7.5. Problem solved. Seems it was a problem with Ventura. There was a fix that addresses out of bounds memory addressing:

GPU Drivers

Available for: macOS Ventura

Impact: An app may be able to cause unexpected system termination or corrupt kernel memory

Description: An out-of-bounds write issue was addressed with improved bounds checking.

CVE-2025-24273: Wang Yu of Cyberserval

CVE-2025-30464: ABC Research s.r.o.

Seems like this may be the one that fixed it.

[cephotographyuk]

Also just updated to Ventura 13.7.5. Problem seems to have been resolved. Thanks @roberts77626518 for the update. Oddly, enough I decided to send a recent crash report to Apple 'just for the hell of it' as Adobe's communication on this issue has been extremely dissapointing - even if it was an Apple issue.