Edit changes are slow to appear

[Christophe5DE8]

Good evening,

After having tried pretty much everything I could find or think of, I'm calling for help from the community, out of despair 

Since LR 14.4, I barely can develop my pictures anymore:

• The Develop interface is very slow / lagging,
• The changes I try to apply seem to be queued, and executed with a massive lag,
• However, the changes I apply are applied instantaneously in the Navigation preview,
  Sometimes I *can* work at normal speed, does not last,
• Cropping tool will make the photo disappear from the Develop windows, until I switch pic, or tool, and then i will sometimes
• Switching pictures will make the processing lagging immediately,
• Switching pictures may display the new photos totally mis formed for few seconds
• All this symptoms come and go, I could not find a pattern (Not helping to troubleshooting)

The dev tools are lagging too:

1. If I switch from Color to B&W: I keep seeing the Color Mixer
2. If I switch back to Color, I keep seeing the B&W tools
3. The folded in Histo will fold out second after I asked for it
4. The tools display does not refresh properly

• Library operation seem to lag less, but the Navigator will lag to open if it's closed

My rig:

• AMD Ryzen 7 3700X 8-Core, 3600 Mhz
• NVidia RTX 2060 6G 0 latest Studio Drivers
• 32GB of RAM
• OS & LR catalog of 2 different SSD
• Catalog is about 2.5GB
• Windows 11 up-to-date
• Wired LAN
• RAW on a Synology NAS since 2024

I tried, without success so far the following:

• re-Install the latest Nvidia Studio drivers "fresh"
• Enable/disable the GPU,
• Clear the caches,
• Reset preferences,
• Check the catalog integrity,
• Export a subset of the photos to a new catalog,
• Restore a catalog from before 14.4,
• Create an empty catalog,
• Reboot of course more that I can write

The symptoms could point out to GPU drivers, but disabling the GPU makes no difference.

Any pointers will help...

[Moved from ‘Bugs’ to ‘Discussions’ by moderator, according to forum rules.]

[Per Berntsen]

Please go to Help > System info, click the Copy button and paste in a new reply.

The system info contains detailed information about your computer and your LrC configuration, and is often helpful for troubleshooting.

[Christophe5DE8]

The requested system info

[avalent]

Confirmed, I am experiencing the same. System info here: https://sharetext.io/305c7921

Video of CPU taking 20 seconds to return to idle after simply going to the next image: https://imgur.com/a/bwmOMp9

Going from one image to another, even without any edits applied can take multiple seconds.

The entire HUD will flicker and lag when going to the Crop or Mask module.

There is often plenty of CPU activity while I'm not doing anything, and with sync and build previews in idle disabled.

It appears LR is doing something on its own, whether it's recognizing persons or distractions, even if we're not actively using the tools. It hasn't been this slow for a long time.

When quitting, I'm sometimes presented with the attached prompt asking to wait as it writes to XMP. This is my first time seeing the popup - nothing changed in my workflow. The catalog backups have become huge as a result of Denoise.

All in all, a pretty controversial update so far.

[Christophe5DE8]

the attached prompt asking to wait as it writes to XMP. : confirmed (While I didn't mention it thinking I made the mistake)
System info attached the main post

[Christophe5DE8]

At least i'm not the only one.. I'll take any relief I can 😉

[johnrellis]

@Christophe5DE8 and @avalent, some troubleshooting steps:

1. Have you enabled Catalog Settings > Metadata > Automatically Write Changes Into XMP?

2. Are you applying Denoise to batches of photos at once?

3. If so, after you create a new test catalog and import, say, a dozen photos into it but DON'T apply Denoise to them, does the problem still occur?

4. If you roll back to LR 14.3.1, does the problem still occur?

[Christophe5DE8]

@johnrellis:

1/ no. I found it enabled after the upgrade(as I reported above). Disabled immediately.

2/ i don't use Adobe denoise at all and never used it, other than the manual one. No AI, no batch. 

3/ as i reported earlier, i tried created fresh catalog. No improvement.

4/ will tomorrow

[johnrellis]

@Christophe5DE8: "I don't use Adobe denoise at all and never used it"

That rules out a severe performance bug that can cause editing to get very sluggish.

[Christophe5DE8]

I'm not sure to follow you.

NOT using Adobe AI denoise will render editing sluggish?

[johnrellis]

@Christophe5DE8: "NOT using Adobe AI denoise will render editing sluggish?"

I had a typo in my last reply. Using Denoise with the option Automatically Write Changes Into XMP can cause editing to get very sluggish.  But this doesn't apply to you.

[avalent]

1. Yes, XMP writing's enabled

2. I always use batch denoise

3. Created new catalog, skipped denoise, performance is slightly better

4. I'll avoid rolling back for now because it'll likely cause issues with photos which had non-destructive denoise applied.

So far a new catalog helped some (though I regularly optimized the existing one with 3k photos).

Performance isn't that much better compared to 14.3.1., though I'm seeing a bit faster masking, still have to test with more extensive masking across ~100 photos.

I'd even accept lower preview quality but the new denoise insists on standard previews. I regularly purge both caches since it's an Achille's heel for Adobe (especially After Effects.. what a storage eater that one is).

[johnrellis]

@avalent: "XMP writing's enabled.  I always use batch denoise."

There's a severe performance bug with the option Automatically Write Changes Into XMP used in conjunction with Denoise that causes editing to be very sluggish:

https://community.adobe.com/t5/lightroom-classic-bugs/p-automatically-write-changes-to-xmp-can-t-be-...

The only workarounds are to roll back to 14.3.1 or disable that option. I've done the latter, even though I much prefer having it on.

[Christophe5DE8]

Rolling back to 14.3.1 and I'm back in business.

Something is not ok with 14.4

[Christophe5DE8]

Some updates after the last support call:

As stated initially, upgrading to 14.4 degraded performance basically rendering LrC 14.4 unusable.

1- Resetting the preferences did help for few days

2- last support made me delete the CPU config files (Windows)

A- disable the GPU from the preferences

B- close LrC

C- delete the files

\users<>\ApplicationData\Roaming\Adobe\CameraRaw\Gpu\Gpu.txt

\users<>\ApplicationData\Roaming\Adobe\lightroom\Gpu\Gpu.txt

Disclaimer: currently notnon my computer, so the paths i wrote might not be 100% accurate.

3- restart LrC and re-enable the GPU

In my case, LrC 14.4 came back to life after the deletion of the gpu.txt files. I don't know how long it will last though, more soon, as I will have a lot of photo to work on from 18/8.

And tbh, if LrC goes slow next week again, i will start the painful process of getting rid of it.

[johnrellis]

Normally, when those GPU files are present, LR's Help > System Info will show that the GPU has been disabled or isn't detected. Do you recall if that was the case?

[Christophe5DE8]

It wasn't the case.

And if my memory serves well, the GPU.txt in the \lightroom\ folder got recreated when i restarted LrC.

[johnrellis]

Hmm.  Normally, when the Camera Raw engine detects a problem with the GPU, it writes one or two temp files that will disable LR's use of the GPU until the files are deleted:

https://helpx.adobe.com/camera-raw/kb/acr-gpu-faq.html

And when you do Help > System Info, it should show the GPU as disabled. 

But it sounds like you're making progress, knock on wood.

[saitejagopi2894]

@Christophe5DE8 

Thanks for sharing the update. Could you please try the following steps and let us know if you notice any performance improvements?

Performance Optimization Steps:

1. Go to Edit → Preferences → Performance
2. Under Camera Raw Cache Settings, click Purge Cache
3. After purging the cache, restart your machine

Let us know how it goes!

[Christophe5DE8]

First i did actually.

I cleared Camera Raw Cache pretty much before every single test i ran.

Same for the previews folders, i deleted them before recreating the previews.

[saitejagopi2894]

Just checking—have you restarted your machine since you purged the cache?

[Christophe5DE8]

More that you can think indeed

[2k.Pandey]

This version 14.4 brings the computer to a grinding halt. Yes, the updates are great but what good are those updates if the whole experience of using your computer virtually changes overnight. I've tried on 2 different machines. i7 12700k and i5 13600k, both with 3060 RTX. These are high end machines and rolling back to the previous lightroom version totally solved the problem. Not just LR, even on this machine, my whole computer starts to lag and starts acting like its on 5 GBs of RAM instead of 64. 

I have tried every single solution listed here, restarted multiple times, purged cache, optimized catalog and what not. Nothing works. Plus I've done a lot of work on these new catalogs so I can't even roll back my main machine. 

Its been quite some time since such a buggy update has come through. Please help if someone has found a solution to this except for waiting fo the next release or going back to 14.3.1

[Christophe5DE8]

Actually rolling back is not a good fix either.

lagginess is back on my rolledback installation

[Christophe5DE8]

Some updates, which I can't make sense of.
I contacted the support who made me follow the process to reset the preferences (https://helpx.adobe.com/lightroom-classic/help/reset-preferences.html) - I did take a backup of the to be able to compare later on.
- First time: Symptoms appeared again as soon as I touched Preferences
- I did it a second time, and this time LrC is still responding normally, I can crop etc without noticeable lag.

The comparision between active & bakcup version of 'Lightroom Classic CC 7 Preferences.agprefs" don't show smoking guns.
And I did slowly reconfigure my preferenes to spot potential killer change. So far nothing to report

it *might* be fixed, but it does not make much sense yet