N

2 Messages

 • 

82 Points

Fri, Dec 11, 2020 1:03 PM

Lightroom Classic: Lagging and super slow after updated 10.1 Lightroom Classic

I am having a issue after updated to 10.1 few hours ago. My iMac's fan is running so loud, lagging, and super slow. I can't editing my wedding photos. Especially when I use crop tool, all system just stop for 3 ,4 seconds. Also after cropping done, the preview images are unusualbe. I have to close lightroom and reopen. I'd like to go back to 10.0 versoion, but it's pain in the ass to re-setup all my presets and catalogs.

Now I have to turn off my GPU, and it's working and better, but still lagging.

 

It's the worst update ever. Please fix this issues ASAP Adobe Team! I have to finish my all weddings before this Christmas!!!

Responses

37 Messages

 • 

366 Points

4 m ago

Exactly the same for me. I found turning off GPU helped. But then I actually went back to 10.0, just so much more stable.

2 Messages

 • 

82 Points

Do I need to uninstall current version before install 10.0? That means I have to import all my current presets again, right?

37 Messages

 • 

366 Points

No, just install the previous version (10.0). We did a blog explaining, you might find useful:

https://www.lightroomqueen.com/roll-back-update-previous-classic/

HTH!

(edited)

1 Message

 • 

60 Points

4 m ago

yep Im having issues too. Super slow 

2 Messages

 • 

70 Points

4 m ago

I'm seeing the same behavior. For me, even v10 was slow and especially scrolling was choppy, like waiting up to a few seconds between each screen redraw. 

V10.1 is completely unusable and actually crashed the system. I started suspecting GPU problems, but I was not able to change the settings for GPU as the application was grinding the whole system to a halt. 

Worst upgrade ever from Adobe. At least as far as I can remember. 

I'm on a late 2015 iMac 27 quad core 3,2 GHz with 32 Gb RAM and plenty of drive space. Still running mojave as I've had no reason to switch to catalina. Other apps are working fine, so I don't think anything is wrong with my machine. It started happening after upgrade to LR v10.1. 

Champion

 • 

5.8K Messages

 • 

100.4K Points

f8andbethere, do you have a custom display profile assigned to the display created by a calibrator?

2 Messages

 • 

70 Points

@John_R_Ellis 

I've not created a profile with a calibrator, no. But the iMac comes stock with an "iMac" profile set on the screen. I don't know if that qualifies as a custom profile or not.

I uninstalled v10.1 yesterday as it was not usable for me. Just opening the app halted the system so that I needed to do a hard restart for it to become responsive again. I have two crash logs to share if Adobe is interested, but I don't know where to share them.

1 Message

 • 

60 Points

3 m ago

Having the same issue! Just updated Lightroom Classic today, but didn't help. Getting the same glitchy pattern as you, and I can barely do anything without a few seconds lag or a crazy glitch.

Running Catalina 10.15.7 as well, on a mid-2015 MacBook Pro

1 Message

 • 

66 Points

2 m ago

I am having similar problems on my Dell Windows computer. I've tried all the performance recommendations and it's still 3-4 clicks behind.  Frustrating!

3 Messages

 • 

82 Points

2 m ago

Same here with a MacPro with 64GB of RAM and internal SSD.

I have certain tools that do not work sometimes, I have to restart and then they do.

If this does not improve I will consider to switch to a competitor program.

Shame but after 15 years I am tired with Adobe.

Best Bernd 

Best Bernd

2 Messages

 • 

70 Points

I am having the same problem. I am using Lightroom Classic v 10.1.1.  The issue seems to occur most rapidly when doing a Photo Merge, any type. The trouble appears to be a memory leak. When the system slows down, I pull up task manager and notice that Lightroom is using over 16GB of RAM. Restarting Lightroom, I see that it takes several seconds for the memory usage to drop to zero and the program to shut down. My system is a 3 GHz 64 bit Intel i7 processor with 32 GB RAM no way it should be eating that much memory.

(edited)

Maestro

61 Messages

 • 

566 Points

YES. 

I have noticed this as well. If I quit LRC and restart it after every one or two image edits, it is faster. The more images I try to edit (composite HDR layered with 10-20 strobe layers for architecture), the slower it goes, until it eventually fails. 

Looking at the Activity Monitor, LRC (and PS too) are just gobbling up RAM that they cannot possibly 'need' (I have 48GB in 16x3 config) and there's no way it should need that much. 

Eventually, if I do not reboot the app preemptively, LRC will hang and require 'Force Quit", or eventually the whole computer will 'freeze' (cursor moves, everything else is completely unresponsive). 

I also have a whole bunch of other weird problems, such as when using "open as layers", if I have over about 12 layers, it will sometimes open the second-to-last selected image *twice*, but it will give it the 'file name' of the last selected image anyway. 

It's just a complete disaster of a release, in every possible way. Beta releases are more reliable than what Adobe puts out. If I can finally get caught up on my three month editing backlog, my first move is going to be to start testing Capture One, install Photoshop CS6, and otherwise wash my hands of Adobe. They have truly hurt me too badly this time. 

Maestro

61 Messages

 • 

566 Points

1 m ago

Thousands of professionals are experiencing this problem. If at all feasible, your best option from everything I'm reading is to backup your LRC 10 catalog (files and library) and put it on a shelf. Re-install LRC 9.4 and it will work again.

You can also try turning off GPU acceleration and custom monitor profiles, but for me and many others, it made little difference. Maybe you'll get lucky. 

There is currently no word from Adobe on a fix for LRC 10, and it has been several months. If your income depends on it, there seems to be no other solution except abandoning Adobe LRC and moving to Capture One, which also has its limitations depending on your workflow. 

2 Messages

 • 

70 Points

1 m ago

Using task manager, I don't see the GPU in use, just memory usage creeping up even if you are doing nothing. The only work-around is to shutdown Lightroom, wait 30 seconds, then restart,  you don't have to restart the computer. Downgrading to LRC 9.4 may not be feasible as the database has changed and you will lose all the edits you have made, the photos will still be there just the changes.

3 Messages

 • 

82 Points

@bwalk7217 

Well one way to keep the edits in HiRes would be to open them - with edits - in PS and save them as tiff.

Then you have two version one original and one with the latest edits - at least.

Best Bernd 

Best Bernd

Maestro

61 Messages

 • 

566 Points

True, but I would have to convert a library of over 500,000 RAW files to do this. So... Another $3k on a new RAID array and drives, and about two weeks of 'waiting' for it to convert and export everything, while already being months behind on deliverables. This whole situation is just infuriating. There seem to be no good options. 

Maestro

61 Messages

 • 

566 Points

@bwalk7217 FWIW:

PS is set to allow use of up to 32GB of RAM (70%). 

Scratch disk is set to a RAID 0 array with 6k MB/s i/o. Extremely fast, but not as fast as RAM. 

Activity Monitor RAM use observations: 

When I launch LRC, and do not touch a single thing (just static open app), it starts at about 680MB RAM use, and slowly builds up to 4GB RAM use and holds at that level. 

When I open Photoshop, it will open at around 680MB RAM use with zero files open.

Then, if I select just six RAW files (50MP Fuji GFX lossless compressed FWIW), LRC goes up to 5GB RAM used, and then I select "open as layers in PS", and PS opens the files and goes to 5GB RAM used as well (with 6 layers). 

When I duplicate one layer, RAM use by PS is unaffected.

As I build masks for all the layers and make numerous adjustments the PS RAM use builds to 7GB. When I flatten the image it goes up to 8GB.

When I save and close the window, PS RAM use remains at 8GB. 

LRC RAM goes up to 6GB at that point. Then, in LRC, I apply lens corrections, and it remains at 6GB. I apply some spot brush corrections and it rises to 6.5GB. (PS remains at 8GB, with no files open, sitting in the background).

Next, without quitting and rebooting LRC or PS, I move to a file with more layers. I apply "Basic" corrections to one file, and sync it to 15 others. No rise in RAM use. Then make individual 'basic' corrections to the 15 files one at a time. LRC RAM use falls back down to 6GB. Merge 5 50MP brackets to HDR, and LRC RAM use goes up to 10GB. After merged to HDR complete, it goes down to 8GB. 

Then I apply several different adjustment brush changes to the HDR file, and it rises to 12GB RAM used. Then select 14 files and 'open as layers in Photoshop'. LRC holds at 12GB, PS rises from 8GB to 9GB once the files are all open. 

Once I start applying layer masks and making edits, PS grows to 10GB. LRC just holds at 12GB, unused in the background. As I continue to make brush strokes to layer masks, PS RAM use grows to 11GB and then 12GB. 

Switching to LRC to review a few RAW files for consideration in the composite sees LRC rise from 12GB to 13GB.

So, now LRC is just over 13GB, and PS is at 12GB (with 16 layers). Flatten the layers and nothing changes. Presumably because it's holding all the 'history' information. 

Then I flatten and save the PS image, and switch back to LRC. RAM use holds at 13GB for PS, and 12GB for LRC.

Then I do another HDR merge in LRC, and LRC goes up from 12GB to 16GB. Start making 'Basic Edits' to individual RAW files in LRC, and it goes up to 19GB. PS, with no files open, rises to 14GB. And it just continues. Select 8 files in LRC and "open as layers in PS" and goes up to 20GB, and PS rises from 14GB to 15GB. 

So, basically, it seems like neither LRC or PS are purging their RAM use, and it just builds and builds until the RAM is maxed out. Before logging the above, I had opened Activity Monitor and seen PS up toward 30GB RAM use, and LRC at 14 GB, sputtering along until it just finally 'freezes' because it's eaten all the available RAM resources, and is forced to start purging the RAM it's hoarding, but hoarders aren't any good at purging...

That all said, it seems like another important aspect of using this flawed, no-custom color calibration beta-ware is to close it and reopen it after every few composite photos to keep it from eating itself sick. 

(edited)

3 Messages

 • 

82 Points

Well the memory use is not the problem for the lag.

I have 64GB and way mem left and it does stutter.

Programs keep things in cache in case you would use it again.

Nothing unusual - they clean the mem with new items - say swap it out.

That IMHO is not the cause for the lag - it is a  bug in the processing part.

Best Bernd 

Best Bernd

Maestro

61 Messages

 • 

566 Points

That's what I would expect, to a degree, but once PS saves and closes a completed file (sending it back to LRC, essentially), there's no reason for it not to clear it's RAM use at that point. But with each round-trip from LRC to PS and back to LRC, it just takes more memory and never releases it until it maxes out the RAM, which results in increased and extreme lag as it nears the max, ultimately causing the software to hang/freeze, or causes the whole system to hang (at which point Force Quit and Finder don't work, necessitating a hard reboot. 

The same for LRC. As it hoards more and more RAM, it becomes more laggy. LRC 10 never behaves fluidly or snappy in the first place (i.e. when first opened), but tracking RAM use now on Activity Monitor, the performance clearly degrades rapidly as both PS and LRC get closer to maxing out the available RAM. 

My ECU is the same stock unit I bought it with in 2010, the RAM is decent quality 16GB/x3 1333 Ghz, the GPU acceleration is switched off in PS and LRC (RX580 8GB), I'm not running a custom monitor profile (hugely annoying, basically flying blind), and the machine otherwise runs Mojave great (outside of Adobe). I do not have OpenCore installed either. 

(edited)