Corrupted images and catalog

[berliner_ffm]

Since the latest release I had more than a few instances, where Lightroom suddenly hangs and crashes and will not load the current catalog again, without crashing immediatly.

The only way to start LR in these cases is to

• remove the last edited image from the folder,
• then restart Lightroom,
• remove the image from the catalog
• put an older version (restored from backup) of the image back into the folder 
• reimport the image (and redo the edits)

Using an older backup of the catalog is also possible, but then the database has lost all edits since the last backup and not only the edits of the last image.

I included some sample images, with whom I could reproduce the behaviour.

Example images (corrupted and non-corrupted versions) 

[F. McLion]

What exactly do you mean with "corrupt"? I can open all the example images.

Please post the first two blocks (approx. 45 lines) from Help / System information.

[dj_paige]

No need to re-import, just put the backup into the folder.

Your title says "Corrupted" and you provide example of corrupted images at some link, but normally I won't click on a link if I don't know the web site. So I would like you to please show us a few screen captures of these corrupted images by clicking on the "Insert Photos" icon here in the Adobe community.

Corrupted images are always caused by a hardware malfunction somewhere, could be hard disk or memory or GPU or card reader, etc. Corrupted images should not cause LrC to crash, but maybe the crash causes the corruption of images.

[berliner_ffm]

Thanks for the suggestions.

Screenshots are not really helpful here, since Lightroom will immediatly crash on start. So there is not really anything to show.

Putting just the old version of the image in the folder does not help. Lightroom will still crash immediatly. The only way I found was if the image was removed and then reimported or an older backup of the catalog was used.

Strangly I can import the "corrupted" image into another catalog on the same machine (just tested that today).

I agree it must be some kind of hardware<=>software issue. The crash report tells me that there is an Access Violation Error.

I also attached the crash log.

I also tried to disable the RT3070ti (no effect) and turned of GPU-Accelleration with no effect.

The thing that all images that caused trouble had in common was the usage of the new point color tool (no excessive use, just 1 or 2 corrections). 

Here is my system config:

Lightroom Classic-Version: 13.0.1 [ 202310121438-d2af310c ]

Lizenz: Creative Cloud

Spracheinstellung: de

Betriebssystem: Windows 11 - Home Premium Edition

Version: 11.0.22621

Anwendungsarchitektur: x64

Systemarchitektur: x64

Anzahl logischer Prozessoren: 16

Prozessorgeschwindigkeit: 3,2GHz

SQLite-Version: 3.36.0

CPU-Auslastung: 1,0%

Integrierter Speicher: 31940,7 MB

Dedizierter GPU-Speicher, der von Lightroom verwendet wird: 55,7MB / 8032,0MB (0%)

Für Lightroom verfügbarer phys. Speicher: 31940,7 MB

Von Lightroom verwendeter phys. Speicher: 1882,0 MB (5,8%)

Von Lightroom verwendeter virtueller Speicher: 2129,0 MB

Anzahl GDI-Objekte: 711

Anzahl BENUTZER-Objekte: 2460

Anzahl Prozess-Handles: 6590

Cache-Speichergröße: 293,9MB

Interne Camera Raw-Version: 16.0 [ 1677 ]

Maximale Anzahl Threads, die Camera Raw verwendet: 5

Camera Raw SIMD-Optimierung: SSE2,AVX,AVX2

Virtueller Speicher in Camera Raw: 145MB / 15970MB (0%)

Physischer Speicher in Camera Raw: 72MB / 31940MB (0%)

DPI-Einstellung des Systems: 144 DPI (High-DPI-Modus)

Desktop-Komposition aktiviert: Ja

Standardvorschaugröße: 2560 Pixel

Monitore/Anzeigegeräte: 1) 2560x1600

Eingabetypen: Multitouch: Nein, integrierte Toucheingabe: Nein, integrierter Stift: Nein, externe Toucheingabe: Nein, externer Stift: Nein, Tastatur: Nein

Informationen zum Grafikprozessor: 

DirectX: NVIDIA GeForce RTX 3070 Ti Laptop GPU (31.0.15.4617)

Anfangsstatus: GPU zum Exportieren wird standardmäßig unterstützt

Benutzerpräferenz: GPU zum Exportieren aktiviert

[GoldingD]

Two things:

1. In your Sys Info, you left out the library path. Where is this catalog located?

2. From that crash report:

zip_source_win32handle_create

Searching in the community, on that, reveals at least one other posting:

https://community.adobe.com/t5/lightroom-classic-discussions/black-screen-in-develop-module/m-p/1384...

hmm, I was involved in that one. At any rate, are you using MSI Afterburner?

[Keith Reeder]

"Screenshots are not really helpful here, since Lightroom will immediatly crash on start."

Posting screenshots of the corrupted files will get them looked at: like DJ, many of us have a distinct aversion to opening unrecognised sites - especially if we're then expected to down load and open a zip file.

[berliner_ffm]

Thanks for your answers. I attached I screenshot how it looks like when I open the catalog with the image in question beeing present. As soon as I remove the image from the catalog, Lightroom will open again without problems.

I also managed to reproduce that by exporting the single image into a new catalog. I attached that single image catalog too.

I am not using MSI Afterburner, nor is my CPU or GPU overclocked.

Here are my path settings: 

Anwendungsordner: C:\Program Files\Adobe\Adobe Lightroom Classic
Bibliothekspfad: D:\OneDrive\Documents\Lightroom\CurrentWork\CurrentWork-v13.lrcat
Einstellungen-Ordner: C:\Users\jens\AppData\Roaming\Adobe\Lightroom

[berliner_ffm]

Somehow I cannot attach the catalog here. So I made it available here. The image for the catalog was attached to my previous post

[GoldingD]

Bibliothekspfad: D:\OneDrive\Documents\Lightroom\CurrentWork\CurrentWork-v13.lrcat

Does that mean you are keeping a sync on OneDrive?

or

Does that mean your catalog is on OneDrive?

I suspect the former, if the latter, that is just asking for corrupt catalogs

If the former, if the OneDrive sync is lagging, then LrC will get fouled up, at least in terms of performance, but possibly in terms of LrC crash.

Do not use OneDrive in any form with LrC. If you want to backup your photos to OneDrive, accomplish that separately. Not in tandem with LrC.

Lots of examples in this community with library paths looking like that (having OnDrive in the name) that are having nothing but issues.

[GoldingD]

If I have the translation correct. And I had to type in as opposed to copy paste, so I could have fouled that up.

Adobe Lightroom Classic musss authrund eines fehlers geschlossen werden

Adobe Lightroom Classic has to close due to an error

I assume from your screenshot, that you clicked on those tree dots, and that error message showed up.

[berliner_ffm]

Although this is a Onedrive folder, the sync is not active. This would also not explain why the catalog opens if the image is not present and the catalog crashes immediately after start if the image is in the folder.

Regarding the screenshot. The crash happens immediatly. I cannot click anything before LR crashes. The three dots are the only thing that all "corrupt" images had in common, which leads me to conclude, that the reading operation is causing LR to crash.