Lightroom Classic crashes after changing photo location

Report · Oct 31, 2023

I've been having this issue for as long as I can remember, still with no fix. I had an agent via chat take over my system twice before with no resolve. It is incredibly time consuming to try to work through this, both the issue itself and trying to get someone via chat to even respond.

Lightroom Classic keeps crashing after I point a photo to its new destination. For instance, if I imported photos that were at C:\PhotoLocation and then moved it to G:\PhotoLocation after delivering a gallery to a client, once I point Lightroom to the new location and after browsing through that collection for a few seconds, Lightroom crashes 100% of the time.

Latest version of Lightroom (13.0.1), on Windows 10 Pro.

Report · Oct 31, 2023

Please post your System Information as Lightroom Classic (LrC) reports it. In LrC click on Help, then System Info, then Copy. Paste that information into a reply. Please present all information from first line down to and including Plug-in Info. Info after Plug-in info can be cut out as that is just so much dead space to us non-Techs and it takes up vast amounts of scroll space making the reply less readable and less likely that others will bother with your post.

Report · Oct 31, 2023

Thank you, here it is:

Lightroom Classic version: 13.0.1 [ 202310121438-d2af310c ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.19045
Application architecture: x64
System architecture: x64
Logical processor count: 12
Processor speed: 3.7GHz
SqLite Version: 3.36.0
CPU Utilisation: 1.0%
Built-in memory: 32694.2 MB
Dedicated GPU memory used by Lightroom: 112.1MB / 12129.0MB (0%)
Real memory available to Lightroom: 32694.2 MB
Real memory used by Lightroom: 796.0 MB (2.4%)
Virtual memory used by Lightroom: 898.7 MB
GDI objects count: 802
USER objects count: 2917
Process handles count: 2211
Memory cache size: 52.8MB
Internal Camera Raw version: 16.0 [ 1677 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 12MB / 16347MB (0%)
Camera Raw real memory: 12MB / 32694MB (0%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Standard Preview Size: 2560 pixels
Displays: 1) 2560x1440
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info:
DirectX: NVIDIA GeForce RTX 3060 (31.0.15.4584)
Init State: GPU for Export supported by default
User Preference: Auto

Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: E:\Mello2023\Mello2023-v13.lrcat
Settings Folder: C:\Users\Aiden\AppData\Roaming\Adobe\Lightroom

Report · Oct 31, 2023

This was left out, sorry:

Installed Plugins:

1) AdobeStock

2) Flickr

3) HDR Efex Pro 2

4) Nikon Tether Plugin

Report · Oct 31, 2023

Graphics Processor Info:
DirectX: NVIDIA GeForce RTX 3060 (31.0.15.4584)
Init State: GPU for Export supported by default
User Preference: Auto

Interesting that the bit about GPU for Export is missing (or did you leave that out)

Here is that part of System Info on my rig for example:

Graphics Processor Info:
DirectX: NVIDIA GeForce RTX 3070 (31.0.15.3758)
Init State: GPU for Export supported by default
User Preference: GPU for Export enabled

Another observation is that GPU driver version of v545.84 (I think released on 10/18/2023). I suspect that is a Game Ready driver, not a Studio driver. When I bring up the NVIDIA Driver site (Ref 1) I see the current Game Ready driver is v546.01 (released 10/31/2023) , and the Studio is v537.58 (released on 10/10//2023)

You may want to see if a GPU driver update helps. But you may actually want to see if reverting to the older Studio driver helps. Studio drivers are supposedly more tested, more secure, and recommended for creativeusers as opposed to Gamers.

REF (1): https://www.nvidia.com/download/index.aspx

Report · Oct 31, 2023

Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: E:\Mello2023\Mello2023-v13.lrcat
Settings Folder: C:\Users\Aiden\AppData\Roaming\Adobe\Lightroom

vs

I imported photos that were at C:\PhotoLocation and then moved it to G:\PhotoLocation

some points:

Ok, the catalog is on drive E, a hard drive I assume, Ok, fine
The Photos are initially on drive C? Your root/boot drive, Ok Photos can be on any hard drive, no issue.
You move (In LrC correct??) the photos to drive G Should be fine, but....

Four questions

Why are the photos originally on drive C, if they are going to be moved at some point to drive G (may be a personal workflow difference, and to each their own)
What type of drive is G?
Do you have issues with photos initially imported into drive G as opposed to C, then G?
Does drive G have a hardware problem, is it failing??

Note, to clarify question 3. If you import in LrC photos to a destination on drive E, does LrC give you issues?

Report · Oct 31, 2023

That was simply for reference to this issue. Typically my workflow is as follows (keeping in mind C: is boot drive):

Catalog is on E drive, an internal SSD
Import photos to G, another internal SSD
Do all my edits and such, deliver to client
Once files are delivered or after say 3-6 months, I'll then move said photo folder (G:\DateOfShoot) to an external LaCie HDD (M:\DateOfShoot) for storage / archival, occasionally referencing back
Once I go into the catalog with said collection and select this new location on M is when the crashing happens

To answer question 4, this issue has stayed present with different drives, different catalogs, etc. with the above workflow. Hopefully this clarifies some details, thank you for your responses!

Report · Oct 31, 2023

When you move to G, is that within LrC via the Folders Panel, or outside LrC via Windows File Explorer?

Report · Oct 31, 2023

Did you mean move from original import location of G to then archival drive of M? That is done via explorer. Otherwise, I import from camera to LR directly (to G)

Report · Oct 31, 2023

That is done via explorer.

And as such LrC looses track of the photos, they are then missing photos. Can be a problem.

https://www.computer-darkroom.com/lr2_find_folder/find-folder.htm

Report · Nov 01, 2023

This is what I do. I click the "!" to find the missing photo / folder (for instance moved now to M) and once it reconnects the two, once I begin browsing through that folder of photos is when LR crashes.

Report · Oct 31, 2023

A small followup, a P.S. in support. Not about solving your problem, but about file/folder//app locations as it relates to performance in/for LrC

The catalog MUST be on a hard drive attached to the computer. Either internal or External.
The catalog CANNOT be on a server share, such as a NAS, an actual Server, or the Cloud
You will see some with catalogs on server shares. Some may advise as the best thing since sliced bread, Both NAS and DropBox fans. But Adobe does not support, and it eventually fails. (corrupt catalogs)
The catalog can take advantage of being on your fastest hard drive (performance)
The Camera RAW CACHE can take advantage of being on the fastest hard drive
Some recommend on WINOS, to not place the Camera RAW CACHE on the same hard drive as the Windows paging file (typically C) as the two will have read/wright competition (this might have changed post SSD)
The Camera RAW CACHE does not have to be on the same hard drive as the Catalog.
The Photos can be on any hard drive attached to the computer. Either internal or External
Some disagree, Adobe has no comment. But do not put the Photos on a Server Share. But if you do, the typical problem is LrC missing the photos, probably a continuity issue with LrC seeing the share (members often have this issue if they use a NAS)
The photos do not take advantage of being on the fastest hard drive
The photos do not have to be on the same hard drive as the catalog
Some apparent issues with having an live OneDrive sync with either the photos or the catalog. Might be advised to not do so.

Report · Nov 01, 2023

Wondering if the catalog is corrupt?

Report · Nov 01, 2023

It's happened with every / any catalog.

Report · Nov 06, 2023

Sadly still no fix here.