LRC Crashing when switching images in Develop

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)

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)