Copy link to clipboard
Copied
Hi there, I've go a huge problem with LrC version 13.x.x. The first version I've tested was 13.0.1 and it was a catastrophe. So I switched back to 12.5. with all the hassle that comes with going back to an older catalog version. I've skipped 13.0.2 and now I thought I'll give 13.1.0 a try. At first it seemed to be okay, but it got worse.
The crashes happen randomly. There's no pattern to it. Sometimes it's happening while working with LrC (I had the suspicion that Point Color might be the cause - but it's not), sometimes it's happening while the program just sits in the background and I'm doing something else and sometimes (I might better say often) it crashes during startup. It's not uncommon that I need 3-5 tries to get it started.
My latest (and also current experience):
Since it was running relatively stable the last few days (maybe only 1 crash per day), I upgraded the Excire Search plugin yesterday. After that Excire has to reinitialize all images. I initiated this and did not use LrC. This morning it was still running and of the approx. 130,000 images about 80,000 were initialized. Hooray! (I thought)...
Then this morning I made a huge mistake! I was looking for an image in my catalog for export. LrC crashed and since then I can't get it to work.
It is estimated that 75% of my starts today lead directly to a crash. When it does start, it crashes after about 1 minute (whether proceed to do something with the program or not).
I have since been able to turn off GPU support as a test because I had read in another similar post that there can be problems with graphics cards (or drivers) that are too old. But that didn't help either.
PLEASE ADOBE - I don't want to switch back to 12.5 already (especially since I might lose some changes to my images or they weren't even imported in my backup catalog yet.
What can I do? I have work to do and my customers are waiting.
BR
Thomas
Here's my system information:
Copy link to clipboard
Copied
Update: I've deactivated all plugins except for Excire Search. It seems to be okay, since the plugin continues to to the re-initialize for the missing images. But remember: yesterday it worked fine, too, even all night long until this morning, when I dared to search for a picture. So I can't really trust it. I would prefer it if Adobbe could read something from my crash reports, which I have sent automatically.
Copy link to clipboard
Copied
"DirectX: NVIDIA GeForce GTX 1060 6GB (31.0.15.3640)"
That driver is 7 months old. It may not be the cause of your crashes, but LR is very sensitive to driver bugs, and different versions of LR react differently to different drivers. It's good hygiene to run LR with the latest Nvidia Studio driver:
https://www.nvidia.com/download/driverResults.aspx/216926/en-us/
Copy link to clipboard
Copied
Disabling all the plugins (which you've done) is a good troubleshooting step to narrow down the cause. Of your installed plugins, I believe these have LR tasks or external helper processes that start automatically and run continuously in background:
Copy link to clipboard
Copied
Alright. I will update the driver. At the moment the Excire plugin is working, so I don't want to touch anything. Maybe indeed a plugin problem? Since all of them except for Excire are disabled...
Thanks for your feedback on this.
Copy link to clipboard
Copied
"I would prefer it if Adobbe could read something from my crash reports, which I have sent automatically."
If you attach one of the crash reports here, sometimes we can get a good idea of which features / parts of LR might be causing the crash and narrow down the troubleshooting.
Copy link to clipboard
Copied
I could do that. Where do I find those reports (Windows)? But I fear that there will often be no crash report at all.
Copy link to clipboard
Copied
Hey, @photopoeth. Rightly said by @John R Ellis. I'll share my observations.
One of the things that stood out to me is the number of Config Flags you have & the errors that follow. Try removing the Config.lua flag from the Lightroom Preferences folder.
Secondly, is the catalog on an external drive? As a test, move the catalog or one of the most recent back-ups to the internal drive & check if it helps.
In the meantime, I've checked the crash reports & notified the team to review.
Let us know how it goes. Thanks!
Sameer K
Copy link to clipboard
Copied
Alright, so you mean getting rid of the config.lua in c:\Users\<user>\AppData\Roaming\Adobe\Lightroom\ folder. I think that renaming the file would do the job.
The catalog is on an internal SSD.
Good to know, that you're looking into the crash reports.
As I said: at the moment it's running without crashing and the Excire plugin does it's job. There are only another 49.000 images to initialize.. š So I will let it run without touching ("never touch a running system") until either the plugin finiches its job or another crash happens.
Copy link to clipboard
Copied
I removed the text from here and posted it as a reply to my original post further up. I don't know how to delete a reply completely.Update:
After the Excire plugin was finished, I activated the Anyfilter plugin to find some images that could not be initialized.
[...]
Copy link to clipboard
Copied
sometimes it's happening while the program just sits in the background and I'm doing something else
Copy link to clipboard
Copied
sometimes it's happening while the program just sits in the background and I'm doing something else
No
Yes, sometimes it is.
Not so often, but it could happen, too.
Yes, I do.
By @GoldingD
Copy link to clipboard
Copied
2024-Jan-19 Update #1:
After the Excire plugin was finished re-initializing my images, I decided to work a bit in my library to see if I encounter any crashes. Therefore I activated the Anyfilter plugin to find some images that could not be initialized by Excire.
It worked well and I had NO CRASH at all!
I then closed LrC and performed the suggested actions:
1. updated the graphics driver (tip by @John R Ellis )
2. removed config.lua (tip by @Sameer K )
The (sad) result so far: LrC crashed twice after a few seconds (without any action from me). Now after the third start it runs (also without any action from me so far).
Here's the current system information: ------------------------------------------------------------------------------------------------------------
Copy link to clipboard
Copied
2024-Jan-19 Update #2:
As I mentioned in my Update #1 after the 3rd start LrC didn't crash by itself so I decided to work on 2 images for a client. After probably 20 mins. LrC crashed (while using the healing tool - but I don't think this is important). Now I am not able to get it up and running: sometimes it crashes while starting, then it crashes after a few secs. I tried to disable the automatic XMP saving, but it's not possible becuae of LrC crashing on my way to do this.
This is depressing š @Sameer K Hopefully Adobe finds something in my crash reports
Copy link to clipboard
Copied
2024-Jan-19 Update #3:
In the meantime I was able to deactivate the automatic saving in XMPs - didn't help. LrC keeps crashing and crashing - no working possible.
Copy link to clipboard
Copied
Reviewing the thread, I think it would be good to rule out Excire Search as well by running LR for quite a while with it disabled.
Important: After disabling a plugin that may have background tasks running, restart LR. Many plugins won't notice they've been disabled and stop their background tasks.
Copy link to clipboard
Copied
Yh, maybe that's a good idea. I will try... the problem is: even if it runs for quite a time, it doesn't mean that it doesn't crash the next minute. That's why I would appreciate if I could find the cause without just trial and error.
Copy link to clipboard
Copied
"That's why I would appreciate if I could find the cause without just trial and error."
In this instance, I think the only alternative to narrowing down the cause by trial-and-error is to have an Adobe developer spend some time examining the crash logs. Sometimes they do that, sometimes they don't, but it rarely happens quickly. At least Sameer has confirmed he found the crash reports you submitted and has sent them to the developers to review.
Copy link to clipboard
Copied
I really hope that happens. Thank you @Sameer K!
I agree with the well-known phrase:
"Testing can only ever prove the presence, but never the absence of errors."
Edsger Wybe Dijkstra, The Humble Programmer, ACM Turing Lecture 1972
Copy link to clipboard
Copied
Another Update: I finally got LrC up and running yesterday. After that I didn't change anything e.g. disable Excire plugin. On the contrary, I have tested Excire Search quite extensively and I haven't had a crash since. My computer has been on all the time since the LrC's successful restart yesterday (> 24h) and LrC is still running without crashing.
And that's exactly what I meant: I won't be able to solve the problem just by trial-and-error. Imagine I had deactivated Excire. Then the conclusion would have been that Excire was the reason.
But in reality I haven't changed anything and nevertheless I haven't encountered any crashes since yesterday. But the crash can come at any time. I refuse to believe that problem will just disappear by itself. š
Copy link to clipboard
Copied
After your next crash, leave Excire turned off for twice as long as it is from right now until the next crash. If you can go without a crash for very long periods with Excire turned off, then that is stronger evidence.
Also, run Windows hardware diagnostics repeatedly. If you have an intermittently flaky memory chip, LR can be more likely to trip over it because it uses much more memory, more heavily, than nearly all other typical apps. Ditto for the disk and external USB connections.
Copy link to clipboard
Copied
I can see what you're going for. But what I'm wondering: why didn't I have any problems until I upgraded to 13.x? Version 12.5 ran without any problems. I can't rule it out, but I can't imagine that it's actually Excire or a hardware problem.
Above all, the previous version of Excire was still running until a few days ago and I also had crashes with LrC 13.x. And do you really think that versions below 13.x where more robust to hardware failures?
Again: it is possible, but I doubt it. To me it seems more of a SW problem with the LrC version 13.x.
Copy link to clipboard
Copied
Your symptoms appear to be rare -- few reports here. So that suggests something that's quite specific to your configuration. Absent Adobe's investigation of your logs, your only alternative (other than to stay on LR 12 or walk away from LR) is to rule out other possibilities (which almost by definition, won't occur very frequently across the LR user base).
Regarding Excire, it's not uncommon for new releases of LR to trip up plugins that worked fine in previous versions, either due to a newly introduced bug in the new LR version or a change in internal behavior that's not a bug but triggers a latent bug in the plugin. (I'm a plugin developer.) So make sure you've got the most recent version of Excire and test that you can run for many days without crash when Excire is disabled.
Regarding possible hardware failures affecting LR 13 but not LR 12, it may be that changes in LR 13 are causing Mac OS to allocate physical memory or access the disk in a different pattern than LR 12, and that LR 13 thus is much more likely to trip over hardware problem. Based on bug reports here, the LR developers continue to make significant changes to LR library internals. LR uses much more memory than nearly any other app, so youl could well encounter memory (or disk) issues only when using LR.
I've seen similar instances over the decades. They're rare, but your issue is uncommon too.
Copy link to clipboard
Copied
Hi John, I really appreciate your feedback. Thanks a lot for that.
Your symptoms appear to be rare -- few reports here. So that suggests something that's quite specific to your configuration. Absent Adobe's investigation of your logs,
Hopefully this will happen one day...
your only alternative (other than to stay on LR 12 or walk away from LR) is to rule out other possibilities (which almost by definition, won't occur very frequently across the LR user base).
As a seasoned LrC user giving workshops to step away from LrC ist not an option. On the other hand if upgrades won't work I may be forced to. š
Regarding Excire, it's not uncommon for new releases of LR to trip up plugins that worked fine in previous versions, either due to a newly introduced bug in the new LR version or a change in internal behavior that's not a bug but triggers a latent bug in the plugin. (I'm a plugin developer.) So make sure you've got the most recent version of Excire and test that you can run for many days without crash when Excire is disabled.
Interesting fact: since 3 days I had not one single crash! I have no idea why and I haven't (at least knowingly) changed anything.
I'm working quite intensively with Excire because I want to do a field report on the new version for our next podcast episode. No problem since then...
Regarding possible hardware failures affecting LR 13 but not LR 12, it may be that changes in LR 13 are causing Mac OS to allocate physical memory or access the disk in a different pattern than LR 12, and that LR 13 thus is much more likely to trip over hardware problem. Based on bug reports here, the LR developers continue to make significant changes to LR library internals. LR uses much more memory than nearly any other app, so youl could well encounter memory (or disk) issues only when using LR.
I am working on Windows, but I think your statement also applies to this. If that's my problem, it's hard to find for me, I guess.
For now, I'll have to be content with the lack of crashes and hope that Adobe finds something significant in my log files. Fingers crossed!
Copy link to clipboard
Copied
Crashes are back! I've worked now for nearly 2 weeks without any crash, when an hour ago it suddenly happened again. š Starting up Lightroom again took me a few tries because of crashing while starting the program. Then I've encoutered a lot of crashes during the first 30 secs. or so.
@Sameer K I haven't heared back from you fpor a log time now. Is there anything happening with my crash reports? This is really depressing. I am loosing money when I cannot rely on Lightroom Classic to run stable. Since I am giving online workshops it's viable for me to use the latest versions at the latest after there have been updates for bugfixes, as should be the case with version 13.
So, please Adobe don't let me down...