LRC Crashing when switching images in Develop

[Goredcar]

In the past couple of months, I have had issues with LRC randomly closing when switching from one image to another. LRC is version 14.0.1. The issue has arisen since the last couple of updates. No crash file, and no info on the cause.  It is very annoying and makes it impossible to get any work done. I have done all the suggested stuff on the web. I have reinstalled LRC twice. GPU is off... smart previews are off. I have lots of RAM (64G) and a fast CPU i9 10900K. Gpu is the RTX3080 Ti. All apps on a 2TB SSD, files on a HD in the computer. No issues with PS, only LRC. No other Apps are affected. 

The problem doesn't seem as frequent in Library but happens consistently in Develop. 

[Rob_Cullen]

If you find you’re having odd problems with Lightroom, resetting Lightroom’s Preferences file can solve all sorts of ‘weirdness,’ so it’s a good early step in troubleshooting.

PREFERENCES RESET

https://www.lightroomqueen.com/standard-lightroom-troubleshooting-steps/

[Goredcar]

Thanks Rob, I will try this!

[GoldingD]

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. Also large amounts of text in a post also render the Translate function inoperable...

[Goredcar]

Thanks... I have posted this additional information.

[GoldingD]

Also, please post a screenshot of LrC /Preferences/Performance/

[Goredcar]

Additional system info as requested:

Lightroom Classic version: 14.0.1 [ 202410161356-30922cfc ]

License: Creative Cloud

Language setting: en

Operating system: Windows 10 - Home Premium Edition

Version: 10.0.19045

Application architecture: x64

System architecture: x64

Logical processor count: 20

Processor speed: 3.6GHz

SqLite Version: 3.36.0

CPU Utilisation: 2.0%

Power Source: Plugged In

Built-in memory: 65436.4 MB

Dedicated GPU memory used by Lightroom: 20.2MB / 12086.0MB (0%)

Real memory available to Lightroom: 65436.4 MB

Real memory used by Lightroom: 2082.5 MB (3.1%)

Virtual memory used by Lightroom: 2472.6 MB

GDI objects count: 895

USER objects count: 2564

Process handles count: 6039

Memory cache size: 1832.5MB

Internal Camera Raw version: 17.0 [ 2043 ]

Maximum thread count used by Camera Raw: 5

Camera Raw SIMD optimization: SSE2,AVX,AVX2

Camera Raw virtual memory: 349MB / 32718MB (1%)

Camera Raw real memory: -2626MB / 65436MB (-4%)

Cache1:

NT- RAM:0.0MB, VRAM:0.0MB, Combined:0.0MB

Cache2:

m:1832.5MB, n:0.0MB

U-main: 113.0MB

System DPI setting: 96 DPI

Desktop composition enabled: Yes

Standard Preview Size: 1440 pixels

Displays: 1) 2560x1600, 2) 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 3080 Ti (32.0.15.6094)

Init State: GPU for Export supported by default

User Preference: Off

Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic

Library Path: G:\LR Cat Backup\LR5 Cat-2-3-2-v13-3.lrcat

Settings Folder: C:\Users\David Oman\AppData\Roaming\Adobe\Lightroom

Installed Plugins:

1) AdobeStock

2) Flickr

3) HDR Efex Pro 2

4) LogiOptions

5) Topaz Photo AI

[GoldingD]

Library Path: G:\LR Cat Backup\LR5 Cat-2-3-2-v13-3.lrcat

The above library path is not the issue. It is probably not causing your problem. But it points out a likely file management issue. Call me OCD, but.

1. Did your catalog at one time fail? And are you now using a backup copy?
2. Is that hard drive where you meant to keep your working catalog
3. Is that hard drive where you keep your backups?
4. Is it perhaps time to consider renaming your catalog?

Consider your file management and your backup strategy.

• https://mastering-lightroom.com/secure-photo-backup-strategy/

[Goredcar]

GoldingD, Thanks for this observation.

1. Did your catalog at one time fail? And are you now using a backup copy?

My catalog has never failed... this is just the default naming convention, which reading between the lines, I hear you suggest simplifying

2. Is that hard drive where you meant to keep your working catalog

I redirected the location of the backups to the HD where most of the image files are - I believe that this is the working Catalog. How could I check this?

3. Is that hard drive where you keep your backups?

Yes, this is the location for the backups. I do have images split across 2 different drives. Both internal.

4. Is it perhaps time to consider renaming your catalog?

Dumb question... I had assumed that the backup was the working catalog... if that not the case and how do I go about renaming. The backup I can change when I ask it to back up, but if the working catalog is in a different location I don't know where that is. 

Also on my second re-install of LRC I did not use past preferances so it didn't know where the catalog was (the first time it did). I directed it to the backup location (pathname as above)

[GoldingD]

2. Is that hard drive where you meant to keep your working catalog

I redirected the location of the backups to the HD where most of the image files are - I believe that this is the working Catalog. How could I check this?

4. Is it perhaps time to consider renaming your catalog?

Dumb question... I had assumed that the backup was the working catalog... if that not the case and how do I go about renaming. The backup I can change when I ask it to back up, but if the working catalog is in a different location I don't know where that is. 

By @Goredcar

Working or Backup?

That all involves your knowledge of what you have filed where. Note that a backup of a LrC catalog via the LrC backup option when closing LrC creates a compressed file. To use that backup you need to copy the compressed file to a desired location (not the same file location as the backup) and un-compress it. Simply double clicking on the compressed backup should fail. So a catalog in a backup folder is probably one you either accidentally placed their or copied and uncompressed, the latter after a LrC catalog corruption.

Call me OCS, but a LrC catalog is a database, and it is best to keep good file management when working with a database, a corrupt file management can lead to issues in a database. And seeing a working catalog in a backup folder just screams ISSUE ISSUE ISSUE.

________________________________________________________

Rename the catalog

With the new LrC version, this is simple. In the Menu Bar, in File (well on a WINDOWS it is File) you will now see a Rename Catalog option.

It is probably best to keep the name simple and short, and perhaps descriptive as you see fit. Now I see you are on Windows, this may not be such an issue on MACOS, but as those catalog file names get longer and longer, you can eventually run against Windows nasty file name limits. Not so much for the catalog, but for the various library preview files, and eventually you will come against Windows complaining about that (and failing to open the catalog). This can be avoided by controlling the file location (not several folders deep) and catalog file name.

Also, at some point the convoluted catalog name, if you let LrC just keep adding to it can get annoying (Although that may have changed at the last upgrade via an option when upgrading the catalog)

 ____________________________________________________________________________

P.S. I see that you do not have the OneDrive issue. This being users who use MS accounts instead of local accounts getting forced by Microsoft to auto sync various User System Libraries (Folders) with OneDrive. Some of these folders are Desktop, Documents, Downloads, Music, Pictures, and Videos. Many members for the catalog library path have their catalog in a subfolder under Pictures, and they have a MS account, resulting in a path that looks something like:

C:\Users\myname\OneDrive\Pictures\Lightroom

or

C:\Users\myname\OneDrive\Lightroom

Should you decide to relocate your catalog to another location, then create a root level folder for that, one the drive you desire, but DO NOT name the folder Pictures, instead select something you like such as MyLightroom, MyPhotos, Rumpelstiltskin, anything other than Pictures, or Documents, etc.

If you use a local account, not a MS account, and as such probably do not use OneDrive, then not an issue (however some would say still avoid the MS Windows folder Pictures, their was one nasty MS Windows update that fouled that folder up, hopefully not to be repeated)

[Goredcar]

I totally agree with you on the problems with OneDrive. I just hate how it automatically takes the entire desktop on my Win 11 laptop. I have disabled as much of it as I can. That is one of the reasons I'm dragging my heels on the Win 11 upgrade on my desktop. I would never save my catalog on OneDrive. 

So I renamed my catalog to something less cryptic... that that was easy to do. I though that perhaps it would save the new catalog to the C drive but it is going to the same place I had it before. It is a bit confusing but the Drive is called G:(Backup), but in fact the working catalog is saved there. It is good to know that the auto backups are compressed. I see them in the Backups sub directory and they are Zip files.

So unfortunate (inaccurate) naming on my part, The dir should not be called LR Cat Backup. LRC is placing the backups in sub directory of the working catalog directory which is located  at G (Backup):\LR Cat Backup - at least its at the root level 🙂

Thansk for helping me to sort this out!

[GoldingD · Accepted solution]

Installed Plugins:

1) AdobeStock
2) Flickr
3) HDR Efex Pro 2
4) LogiOptions
5) Topaz Photo AI

This might be the cause or contribute to the cause of your current problem, the LogiOptions Plugin.

The LogiOptions Plugin, is, or has been, a known piece of trash. Especially if you do not need it. That being said, the one well known issue occurs when batch deleting photos. This plugin causes an annoying error to pop up, the error message being:

• An internal error has occurred: ?:0: attempt to index field 'additionalDevelopMetadata' (a nil value) 

Thier are also some LrC community discussions on this plugin causing LrC performance issues (links at bottom)

If you do not need this plugin, then dump it.

Note that this plugin is not the driver for your mouse or keyboard, nor is it the control app for the mouse or keyboard, despite it's name. This plugin, for capable Logitech mice and one keyboard, allows you to use the extra buttons, and dial (keyboard) to act like a poor mans LoupeDeck. If you do not use that capability, then the plugin is of no use.

some links:

• https://community.adobe.com/t5/lightroom-classic-discussions/lightroom-9-1-slow-start/m-p/10829904#M...
• https://community.adobe.com/t5/lightroom-classic-discussions/blocage-lightroom-classic-12/m-p/133864...
• https://community.adobe.com/t5/lightroom-classic-discussions/10-2-slow-start-quot-not-responding-quo...
• https://community.adobe.com/t5/lightroom-classic-discussions/lrc-slow-startup-or-not-reponding-at-al...
• https://community.adobe.com/t5/lightroom-classic-discussions/lightroom-classic-hangs-on-startup-wind...
•  

[Goredcar]

GoldingD, thanks for this suggestion. I do not use the extra buttons on The Logitech mouse so I have disabled this plug-in. I did some quick jumping around from one image to another in the Develop module and so far so good. I will play with some more and let you know how it goes.

Did you see anything else in my setting that you would change? I disabled by GPU accelerator based on feedback from someone. Can I re enable that as obviously it did not help and should improve performance?

Your help is greatly appreciated and this pronblem was driving me nuts!

[GoldingD]

Did you see anything else in my setting that you would change? I disabled by GPU accelerator based on feedback from someone. Can I re enable that as obviously it did not help and should improve performance?

By @Goredcar

To use or not to use the GPU option typically involves testing. That being said, I notice that you have:

NVIDIA GeForce RTX 3080 Ti (32.0.15.6094) with 12 GB of VRAM

I have:

NVIDIA GeForce RTX 3070 (32.0.15.6614) with 8 GB of VRAM

And my GPU works just fine with LrC with that option on. So other than your driver being a little out of date (not so much that it will matter) I suspect you will want to turn that back on. Had your GPU been a lot older, say a NVIDIA 1xxx series (like a 1070) or older, then perhaps yes. Oh, and if you update your GPU driver, best to select a Studio Driver not the Game Ready, NVIDIA recommends that for Creative use  for non Gamers, the Studio Drivers are more tested.

Not having the GPU option on will slow down or perhaps prevent some of the newer AI offerings in LrC (you may just as well forget AI DeNose)

[Goredcar]

Argg so I turned the GPU back to auto, jumped around to a few different images in the filmstrip and it crashed. Not having access to some of the advanced LRC options is a big deal for me and I couldn't live without DeNoise 😞

I repeated this twice just to be sure. I do think your suggestion to ditch the Logitech plug in was good as I had the GPU off then and with the plug in it would crash. What are your thoughts on the custom setting? I notice a couple of key areas are greyed out. It seems to work and is more stable with custom, but it looks like it would only use the GPU for export, not image processing. 

[GoldingD]

The Custom setting can be  a bit questionable on what it is telling you if you just start out with it checked for export. The fact that items above that are gray does not mean they are not supported, just that they cannot be unchecked in the current state "Use GPU for Export"

But, some have found that the following may help, when it is in Custom, but not working, and if I remember correctly, they had issues with Auto.

1. Starting from bottom, uncheck Use GPU for Export
2. Then uncheck Use GPU for Image processing
3. Then uncheck GPU for Display
4. Close LrC
5. Open LrC
6. You should see an GPU Preferences Dialog talking about your GPU turned Off, not Enabled. This is probably the point of doing the above, to get this dialog, and turning that GPU back on (Enable)
7. Working from top down, turn each one of those back on (some might just select AUTO)
8. One odd bug, some members despite not having a monitor capable of HDR, find that they need to check that Enable HDR in Library button. I have no idea why, and if this is OS dependant. Something to try and accept or reject.
9. I forget if you now need to restart LrC for the changes to take effect.