Lightroom Class Crashing Out Right after Splash Screen - MacOs Sonoma M3 MBP 16"

Report · Nov 28, 2023

Lightroom Classic Crashing Out Right after Splash Screen - MacOs

This is occurring with LrC 13.0.1. Mac OS Sonoma on a new MacBookPro M3-16”/32gb/2TB - migrated from a late 2020 Intel iMac.

Creative Cloud and the Apps (Ps, LrC, Bridge - Photographer’s Plan) were transferred over from a previous Mac running on Sonoma Intel-Mac using Apple's Migration Assistant.

Right after LrC displays the splash screen, the app exits. In numerous starts I have only had one crash report - which I did not capture.

I have …

re-installed the Universal Binary for LrC multiple times via CC,

deleted the LrC preferences on startup,

un-installed CC and re-installed it,

re-booted, etc.

PS and Bridge run fine - it’s only LrC that’s crashing-right after displaying the splash screen.

Any suggestions on next steps, or how to force a crash report ?

I suspect this has something to do with the migration from the Intel machine, although I do not recall experiencing this ever before - and I’ve done it many times.

Is there a current ADOBE tool that will do a complete/absolute purge of all the cookie crumbs in CC and related apps and the apps themselves (more thoroughly than the un-installers that are in each folder) that can do a thorough cleaning job and I can just re-install all of CC from scratch if that is the likely cause.

jc

Report · Nov 28, 2023

https://helpx.adobe.com/creative-cloud/kb/cc-cleaner-tool-installation-problems.html

Report · Nov 28, 2023

...and thanks - that's what I was looking for. It has to be the solution to this problem since, uh, LrC does kinda run on M1's/M2's/M3's (like all my other ones......) cheers, jc

Report · Dec 04, 2023

This is an update on Dec 4th. Following GoldingD, I did install the ADOBE Cleaner tool. I still have the problem - and I need to raise the priority on this issue now as I have exhausted all the things I think I can do.

1. I installed the cleaner tool. Did all the steps to purge the previous installation of Creative Cloud and all its Apps. Moved to trash; emptied trash; re-booted and re-installed. LrC still 'exits' immediately after verifying the new app download and displaying the splash screen - no dump/crash report.

2. I created a separate admin account on the machine and logged into the ADOBE ID from it. LrC DOES run on this. I copied over the catalog and image files from the original admin account and they functioned fine.

3. LrC continues to run OK on the Intel 2020 iMac

I do need a solution for this since this is what the 16" MBP was purchased for. Any thoughts on what else could be crashing it or how I can determine it.

jc

Report · Dec 04, 2023

2. I created a separate admin account on the machine and logged into the ADOBE ID from it.  LrC DOES run on this. I copied over the catalog and image files from the original admin account and they functioned fine.

So, does that mean that something is wrong in your standard user account on that MAC?? Identifying and fixing the problem can be a pain. Perhaps a MACOS guru will reply. Perhaps a new standard user account is called for?

You may want to read:

https://helpx.adobe.com/lightroom-classic/kb/lightroom-basic-troubleshooting-fix-most-issues.html

By the way, you stated a separate admin account, were you previously using an admin account? Normally that is frown on as a cyber security risk. One should normally use a standard account, a non admin account, for daily computer use. Restrict logging on as Admin, for maintenance issues, updates, etc. Mind you, this is higly debated.

Report · Dec 11, 2023

Resolved - I finally determined this ALL had to do with my friend's screwed up arrangement with DropBox. She had both the Documents and Downloads folder configured within DropBox and while that worked on the source machine, it did not work when migrated to the M3 MacBookPro. And thi wasn't the only problem that configuring it like that caused.....hours spent untangliing other issues too.

My main takeaway on this is that if you encounter similar problems, actually setting up a 'test' account and building into that is a good way to differentiate whether it is something environmental in the original account or a hardware or an OS issue.

jc