Copy link to clipboard
Copied
So the newest version of LR Classic has a bug where when importing from an external SSD, photos from a folder to NAS storage, Mac OS goes into full Kernal Panic, locks up, where even the trackpad click feedback starts to lag, then no longer responds and crashes after about 5 minutes of importing rebooting the system. Tried this on M1 Pro as well as M2 Pro running both the current latest Mac OS as well as Sonoma Public Beta. For the Public beta M2 Pro laptop, I ended up wiping and reinstalling the OS which did not fix the issue.
The settings for import were standard with build smart previews and avoid duplicates, as per the screenshot attached. Tried with both external and only internal displays. Nothing else running in the background stopped all plugins and tried with the vanilla system post-reinstall. The screenshot does show local SSD and that did seem to work okay for a few photos that were left to import after multiple crashes.
The SSD is sanddisck extreme 1 TB drive.
Given it's a wedding season for a lot of us, this is a critical bug that needs to be fixed.
See this is what I'm confused about in that statement. Renault drag and drop worksnfornterabytes of data so I dont think it's SMB on Mac OS or NAS.
At the same time if it's Mac OS crashing because of Lightroom it sounds like adobe problem as well. I don't think going back to days of changing DLL in windows by software companies is the route.
Would be nice if the dev team or QA team tested this importing to a NAS in their end to debug it. Seems like subscription dollars are not going into tech de
...Copy link to clipboard
Copied
And as you need to get work done now..
What if you, outside of LrC, use MACOS Finder to copy those images from the source to the NAS, Then in LrC, attempt the import the images now on the NAS (selecting ADD)?
Copy link to clipboard
Copied
That does work, its annoying to create folder structure from multi-day events. I did solve it same way you mentioned.
Copy link to clipboard
Copied
As to a solution. As you receive a Kernel Panic, do you receive a Apple error log? And perhaps a separate Adobe crash log? Techs might get a clue from those.
Copy link to clipboard
Copied
When the operating system itself crashes, that's a bug in the operating system or a driver. By definition, an application should never be able to crash the operating system. Something LR is doing could be triggering that bug, but whatever an app does, the OS should never crash.
Copy link to clipboard
Copied
deleted
Copy link to clipboard
Copied
I suspect Lightroom Classic may not be the culprit here, but confirm LrC has Full Disk Access in System Settings. For Ventura, go to System Settings > Privacy & Security. Click on Full Disk Access in the list. Turn on LrC for full disk access. If Adobe Lightroom Classic is not in the list of programs, click on the + sign at the bottom to add it.
The NAS is a common factor. There are many reports on the web of problems with SMB shares on NAS with the Silicon Macs, including kernel panics. I suggest you look for info about your brand of NAS and what has worked for others with Silicon Macs.
Copy link to clipboard
Copied
The LRC does have full disk access to local and NAS. The NAS is a TrueNAS server so that wouldn't cause any issues. SMB is not great on Mac, however transferring via Finder never causes any issues.
I did get an Apple crash log but nothing from Adobe sadly for the logs, just said that it had to quit and verify catalogue integrity. There are absolutely instances where an application can crash a system, it's not common but it does happen if there is a buffer overflow for example from poorly written software. The odd thing is I have no issues editing even with no previews turned on, same with editing video of the NAS with 4K 422 footage as well as doing large transfers, its only Adobe imports that are causing it, leading me to suspect it could be an Adobe thing more than Mac.
This was never the case in the past release of Lightroom, however after the current update, that's when the issues started.
Copy link to clipboard
Copied
"There are absolutely instances where an application can crash a system, it's not common but it does happen if there is a buffer overflow for example from poorly written software."
If a buggy app does something like that and the operating system crashes, all modern operating systems (Mac, Windows, Linux, IOS, Android) have for decades considered that a bug in the operating system (or driver loaded into the operating system), and they would fix that bug at high priority. A basic principle of operating-system design is that nothing an app does should crash the OS. When there's a flaw in the OS that violates that principle, that indicates a likely security flaw in the OS that malware could leverage to compromise the system.
"The NAS is a TrueNAS server so that wouldn't cause any issues."
As @CumberLinda suggested, the NAS is a common factor among the machines you've tested. Since the OS is crashing, that's a likely suspect.
Copy link to clipboard
Copied
Does rolling back to 12.3 fix it then (using the same import settings)? Have you installed the latest TrueNAS CORE version? It's currently at 13.0-U5.2. If updating doesn't help with importing, check the TrueNAS forums for how owners of Silicon Macs are dealing with these crashes. ChronoSync Arq5, Forklift were all causing OS crashes as of last summer. The updates to CORE may have been a solution.
Copy link to clipboard
Copied
Welp was hoping this would be solved, updated to TrueNAS-SCALE-23.10.0.1, latest lightroom classic and still causes kernel panic when trying to import photos using that route. Windows machine works flawlesly and mac with 14.1 keeps crashing. I can easilly drag and drop photos but i do organization Year/Month/Date and would be swell if this can be fixed between adobe and apple. How is this still going on!
Copy link to clipboard
Copied
Leaving a comment here just to say I also have the same issue. I experience kernel panics when doing a Lightroom import (copy) from my SD card to my NAS (TrueNAS scale). I notice the kernel panic/crash usually occurs after ~250 photos have been copied and then my Mac will become unresponsive.
The mentioned workaround to copy directly onto the NAS first and then doing a Lightroom import works fine but im hoping this could be fixed so the import workflow could be more streamlined.
Copy link to clipboard
Copied
Thanks for the additional information -- that could help others tripping over the same problem.
As explained above, this is a bug in the operating system or NAS driver loaded by the operating system. So it's an issue that can only be addressed by TrueNAS and Apple.
Copy link to clipboard
Copied
See this is what I'm confused about in that statement. Renault drag and drop worksnfornterabytes of data so I dont think it's SMB on Mac OS or NAS.
At the same time if it's Mac OS crashing because of Lightroom it sounds like adobe problem as well. I don't think going back to days of changing DLL in windows by software companies is the route.
Would be nice if the dev team or QA team tested this importing to a NAS in their end to debug it. Seems like subscription dollars are not going into tech debt here
Copy link to clipboard
Copied
Regular drag and drop works for terabytes of data transfer*
sorry for double post, can't see to edit post button
Copy link to clipboard
Copied
Using a NAS can be problematic. This is not an Adobe problem, its a system (most likely the NAS firmware) problem.
Copy link to clipboard
Copied
I've had the same issue for many months. Latest Sonoma version, always most up-todate version of Lightroom Classic. My NAS is Synology. I can import smaller jobs no problem, but the minute I do a larger import like a wedding, I get a full-on kernel panic after a couple hundred photos every time. I resume the import on restart, and it happens again. And Lightroom somehow gets confused and I end up with some duplicates (with "-2" appended to the end of the file name). I don't know why I didn't think to do the copy-to-hard drive first workaround-- thanks for that. Still, this needs to be fixed.