Lightroom Classic CC 7.0 and 7.0.1: Memory leaks and progressive slowness worse than prior version

  • 15
  • Problem
  • Updated 4 months ago
  • (Edited)
I have been using LR since LR 3, and have noticed, like everyone else, that it only gets slower and more buggy with every release. I was suckered into trying CC Classic because news outlets said it was 15% faster in its general actions (moving between photos, selecting multiple photos in grid view, etc) and a friend of mine said it was much faster on his 6-core Mac Pro.

His machine is built for content editing, and he says LR runs slow on it. My machine is not perfect for content editing, but it is not slow, either.

My System:
I run a Core i7-6700K (not Overclocked, but a top of the line consumer offering) using DDR4-2666 Kingston HyperX RAM (which benches in the 99th percentile of all RAM) and an SSD for my temp drive and have tested it while using an external USB 3.0 HDD as well as using the same SSD for my file storage (not ideal setups but it doesn't matter). I also use an nVidia GeForce GTX 650 Ti which scores high in 2D operations (common in GUI interfaces) and very poorly in 3D operations (which are common in image manipulation workflows). This has been taken into consideration when making my assessments below.

General pattern:
The problem is not with any bottlenecks in the system (mentioned above). The problem is, to the best of my knowledge, Lightroom's memory leaks while using the program, on top of it already being poorly written code. This problem even occurs while doing something as simple as opening the program, selecting all photos in a folder and exporting them to a folder and doing nothing else with the computer while this processes.

I have monitored memory CPU usage while using LR for various tasks, and Lightroom has a major problem with using resources appropriately and its performance degrades quickly while using the program. Not only this, but LR appears to have memory leaks that do not show up in the memory resource view.

My Workflow:
In my workflow, I use the Attribute and Metadata filters to help me apply noise reduction based on ISO rating, lens correction based on lens; I have flagged and unflagged photos shown, but not rejected photos; and then I go through these 400 photos one by one to correct their exposures. I use the develop module, because the Loupe View's exposure controls are not precise and therefore are inappropriate for professional edits.

Example:
So, I edited 400 photos the other day. After 50 edits, at most, I find that the program has become nearly unresponsive, hanging for nearly 10 seconds while the next image loads, and must be restarted to continue my edits. I restarted at least 4 times for this particular set. Wise question: Is too much action history being retained and not expunged from the action queue? Is Lightroom organizing its action history and lists using inefficient list models, e.g. recursive lists instead of indexed lists? Has Adobe's LR team ever taken one minute to consider that their program is written incorrectly for the task at hand?

The reported RAM usage in Windows Task Manager at the time of slowing down is an unimpressive 11 GB out of 16 GB, with the rest of the RAM occupied by standby/cached information that Windows should release upon request to the active application (Lightroom).

While editing during one of these sessions (before restarting), I received an error dialog from another background application that crashed and reported it was due to low memory availability. I restarted both Lightroom and this background program, and, after a few minutes of using LR, I received a new generic crash message from the background program. After this I had to restart my computer to flush all of the RAM. The background application is always running and has never crashed before while using Lightroom 6.7 (the background app has been installed for 6 months). It is a very lightweight program, so I know that Lightroom CC Classic 7.0.1 was at fault. Take note that this slowness problem existed in LR 6.7 but it did not force other applications to crash.




Example 2:
I started an export of 300 photographs after editing a dozen of them in LR. I monitored CPU usage during this process and the LR app used, on average only 20% of my available CPU power, bouncing around within the range ~5% to ~50%. I noticed that processing was far too slow, so I restarted the application with the project still selected and immediately ran the export again. This time, the average CPU usage started out at ~90% and maintained that average for a few minutes, but then it slowly crept down closer and closer to an average of ~60%, showing a gradual degradation in LR's performance.

Solution:
Adobe it's time to hire some real professional programmers. You make craploads of money. Your other programs are not nearly as horrendous as Lightroom is, these days. Just move some of your talent onto this project, dump the existing framework and invest in some legitimate change in LR's code base. Oh, and one more thing: get rid of Lightroom CC. It's a ridiculous concept unless you're offering the entire Lightroom CC Classic functionality in the cloud. Your original cloud idea was to offer instant batch processing of photos via a compute cluster, and I don't see how Lightroom CC can fulfill its intended function when you don't even allow batch editing in it.
Photo of AMDphreak

AMDphreak

  • 3 Posts
  • 0 Reply Likes
  • ignored

Posted 7 months ago

  • 15
Photo of Tom de Jongh

Tom de Jongh

  • 18 Posts
  • 19 Reply Likes
This is also my experience.  Just letting Lightroom Classic CC sit idle makes it slow.  I have been restarting Lightroom every 30 or so photos, just to keep it reasonable responsive.  Does anyone from Adobe monitor this forum?  How long until they at least acknowledge there are issues?
Photo of Stephen Shankland

Stephen Shankland

  • 79 Posts
  • 12 Reply Likes
This is more or less the same problem I have on MacOs with a 2016 MacBook Pro. I have to quit and restart frequently. Some of the sluggishness seems to self-repair if I give LR a minute or two but I still see lots of jank and beach ball spinners.
Photo of Barry Young

Barry Young, Director of Engineering, Lightroom products

  • 53 Posts
  • 48 Reply Likes
Official Response
I am sorry to hear about these slowdowns. We are actively investigating all performance degradations that were introduced with LrClassic 7.0. 

Barry
Photo of Dave Hall

Dave Hall

  • 6 Posts
  • 3 Reply Likes

Hello, I too have seen major performance degradation since upgrading to Lightroom Classic 7.0.1 ala Mac Sierra 10.12.6.  Not even going to post me machine specs here, because I can confidently say they are adequate.

I'm a real estate photographer, and I've been a pro user since Lightroom 3.  The biggest increase in performance I noticed was the ability to create many HDR's at once.  Better memory allocation to that task I suppose.  However, overall the product has more degradations than improvements.  

Here is a list of issues I've experienced.

1. Import issues:  File corruption, and very degraded speed.

2. Micro Lagtime between mouse movement and cursor on the screen, while in develop mode.

3. Inconsistent behavior when creating panos and hdrs.  The new file created sometimes ends up at the end of the files sometimes placed with the originals. 

4. WB/Temperature seems off.

5. Lens correction always needs more correcting.

6. Is it me or has anyone else notice more noise issues than usual?

7. Just switching images in the film strip (dev. Mode) is painfully slow.

NOW may be the time to forever ditch LR.  Adobe is now on my official "It Sucks" list.
Photo of Dave Hall

Dave Hall

  • 6 Posts
  • 3 Reply Likes
This reply was created from a merged topic originally titled FAIL: Lightroom Classic 7.0.1.

Hello, I too have seen major performance degradation since upgrading to Lightroom Classic 7.0.1 ala Mac Sierra 10.12.6.

I'm a real estate photographer, and I've been a pro user since Lightroom 3.  The biggest increase in performance I noticed was the ability to create many HDR's at once.  Better memory allocation to that task I suppose.  However, overall the product has more degradations than improvements.  Can't even edit a basic 40 gb shoot.

Here is a list of issues I've experienced.

1. Import issues:  File corruption, and very degraded import speed.

2. Major Lagtime between mouse movement and cursor on the screen, while in develop mode.

3. Inconsistent behavior when creating panos and hdrs.  The new file created sometimes ends up at the end of the files sometimes placed with the originals. NO consistency in this function between catalogs.

4. WB/Temperature seems off. No consistency.

5. Lens correction always needs more correcting. Essentially useless.

6. Is it me or has anyone else notice more noise issues than usual?  I see more noise in my images than with older versions.

7. Just switching images in the film strip (dev. Mode) is painfully slow. So much so, it renders LR useless in meeting deadlines.

8. As usual, poor and generic documentation that is hard to find and access.

9. Inadequate feedback/reporting system for issues.

10. Adobe clients have to work their asses off to solve problems and troubleshoot.  Should be easier.

11. Adobe Classic: Just confuse my workflow some more and add more steps.  That should help our company add dollars to the bottom line (not).


NOW may be the time for me to forever ditch LR.
Photo of Tom de Jongh

Tom de Jongh

  • 18 Posts
  • 19 Reply Likes
Adobe says they are investigating the slowness. Please give us an estimate of how long this may take.  If it's days away I'll wait.  If I don't hear back I will assume it is either too hard or it will take months, in which case I need to jump ship.  In Australia we have fairly good consumer protection laws and I feel I could quit Adobe today and not pay any penalty as the 'item is not as advertised'.  The old Lightroom was OK, but this version sucks.  Tell us what you are doing, and when you are doing it.
Photo of Assaf Frank

Assaf Frank

  • 147 Posts
  • 44 Reply Likes

Hi Tom,

I have asked this question to Jeffrey about a few days ago and this was his reply. it was in another thread this one below.

https://feedback.photoshop.com/photoshop_family/topics/the-new-release-of-lr-classic-has-a-broken-ap...

here is the reply which I have copied here.

"Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

If we're talking about the issue with high core machines, it's being worked on but I don't believe the changes for that will make the next immediate release. (It's a very complex change)"

at least they are working on it, but it has been like that for more than a year so I don't know how urgent it is to adobe. Also, I suspect that the complexity is due to using old code and patching it rather than a complete rewrite like they have done with the new Lightroom cc (cloud). I hope they are now realized they need to rewrite the multithread processing of Lightroom to utilize multi-core CPUs which are virtually everywhere now. It is no longer only affecting high-end users.
(Edited)
Photo of Tom de Jongh

Tom de Jongh

  • 18 Posts
  • 19 Reply Likes
Thanks for your post.  I am running an early 4 core i7 which runs everything else very well.  It's only editing in Lightroom that has become unusable.  I am carrying on working by restarting Lightroom every 30-50 images.  I don't think my PC is a 'high-end' but interestingly every time I come back to view the comments in these forums I see more people with the exact same symptoms I am experiencing.  I have no doubt something will be done eventually.  I am just impatient.
Photo of Ian M Butterfield

Ian M Butterfield

  • 19 Posts
  • 34 Reply Likes
I'd like to add another voice to this.  I was initially thrilled at the speed of LR7 - it was a lot faster but the more I use it the slower it gets.  Slow imports, memory hogging, lack of responsiveness.    Restarting helps but that can take a long time too.  I am paying over £50 per month because I also use Premier and InDesign but LR (and photoshop) is my main work space. 

I really am starting to wonder how much longer am I going to persist paying that kind of money.  There are already viable alternatives for Premier (Final Cut Pro if I move to a Mac), Photoshop (Afinity)  and with Afinity Publisher hopefully going out to beta before too long , that's a potential InDesign replacement.  That only leaves LR.  On One, and Capture One are getting there, Affinity are promsing a DAM before too long aswell.

The bottom line, Adobe, is I want to stay with LR and the rest of the suite of programs, but we can only put up with this for so long.
Photo of Todd Thoenen

Todd Thoenen

  • 22 Posts
  • 7 Reply Likes
I agree.

When I updated to LR Classic CC I had to upgrade the Catalog it took over 24 hours. I should of took the hint and stopped and reverted back to the old version,but I didn't. I guess i thought I've already invested the time I might as well see what is new and if it is faster. Well I never really got a chance to find out as my system has been crashing ever since I updated. I was told it was my GPU driver so I updated and unchecked use GPU, and it worked for  a while then it started crashing again. I checked my error message files and discovered there was some files and programs that were running at the time, files I don't even use so I uninstalled them. That seemed to work for a while. I was moving files around to optimize space and get rid of duplicates and it crashed. I'm not sure what to do at this point.

To get back to the original comment I tried to import 700 raw images and what used to take 5-10 minutes took over 30. I tried editing an older image from 2009 removing red eye the system crashed, Other than that I haven't even tried to do use develop module.

I would appreciate any advice with this issue. It seems everything I've been told to do has not worked.

My system...
AMD FX 8320 8 core
AMD Radeon RX 480 8 GB with updated drivers
32 gb of ddr5 ram
750 Watt power supply
Samsung EVO 500 gb ssd
Sandisk 1 tb ssd
Sandisk 240 gb ssd
4 Seagate 3 TB internal hdd
EXT drives Seagate 5 TB and 3 TB, and a WD 8 TB
I think that should be adequate to run LR Classic CC the way the old version did
Photo of Emil Lenc

Emil Lenc

  • 2 Posts
  • 1 Reply Like
I have noticed a definite leak when syncing with Adobe Cloud Storage. I have a catalog of ~54000 photos which Lightroom CC has synced to the cloud. Lightroom Classic CC is attempting to sync with this and managed to get through 18548 photos before getting slower, and slower, and slower and eventually exhausting all memory. Now, as soon as I start Lightroom Classic CC it rapidly exhausts all of the memory before I can even do anything with it. I have 16 GB of internal memory and 280 GB of my internal flash drive available but there is absolutely no reason why it would need 70+ GB when just performing a simple sync with the cloud!  e.g.
 
Photo of Tom de Jongh

Tom de Jongh

  • 18 Posts
  • 19 Reply Likes
I have submitted my comments regarding the poor performance of the latest Lightroom and have read replies from Adobe stating they are investigating.Can we please have some information of when we might expect a fix. Maybe Adobe should stop charging or reducing the monthly fee until the software becomes usable. I have made it clear that I am happy to trial any updates or fixes and am willing to pass on any results but have not heard from Adobe despite promises of follow up.
Photo of Alan Novak

Alan Novak

  • 18 Posts
  • 4 Reply Likes
AMDphreak you mention noise reduction.
Guys, among others there is one thing that slows down Develop. It's the behavior of Detail panel.
 Basically, don't touch it before editing and leave all values at default. Apply any NR after edits only.

Check out my earlier post:
https://feedback.photoshop.com/photoshop_family/topics/lightroom-classic-cc-develop-module-still-slo...
Photo of Barry Young

Barry Young, Director of Engineering, Lightroom products

  • 53 Posts
  • 48 Reply Likes
Hi everyone,  The Lr team has been working on these memory slowdowns in addition to being able to utilize multi-core CPUs for certain operations. We would like to invite anyone experiencing performance issues in Lr Classic to our internal development program to help validate some of our findings and to make sure we cover and satisfy expectations in this area. If you would like to participate in this early preview program please email me at byoung @ adobe.com (note the space is deliberate to avoid spam bots) and we will invite you to the program. Include the subject line ”Lightroom prerelease" in the email. 

We look forward to working with you more closely to confirm our findings. 

Thank you,

Barry
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3946 Posts
  • 1362 Reply Likes
Brian, do you want it kept to users on this thread, or can we open it up to a wider audience?
Photo of Ian M Butterfield

Ian M Butterfield

  • 19 Posts
  • 34 Reply Likes
Brian, Thank you for reaching out and working to address this issue. I have emailed you as requested.

There is a related thread to do with similar issues with importing: https://feedback.photoshop.com/photos...
Photo of Jerry Syder

Jerry Syder

  • 182 Posts
  • 88 Reply Likes
Brian?
Photo of Ian M Butterfield

Ian M Butterfield

  • 19 Posts
  • 34 Reply Likes
Sorry, I meant Barry- the problem of trying to reply on a phone where I can’t see the full thread when replying. I got the first letter right... ! :-)
Photo of Jerry Syder

Jerry Syder

  • 182 Posts
  • 88 Reply Likes
Hehehe! It's alright bro, you did. So did Victoria.. just my first giggle of the day :-). Now back to work ha!
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3946 Posts
  • 1362 Reply Likes
LOL Oooops, I shouldn't reply to forum posts at 6am pre-coffee, clearly!
Photo of Ian M Butterfield

Ian M Butterfield

  • 19 Posts
  • 34 Reply Likes
Well, I am blaming Veronica... I mean.... Victoria then... !
Photo of Jerry Syder

Jerry Syder

  • 182 Posts
  • 88 Reply Likes
Where are the emoticons when you need them. I'm sure Brian would forgive you
(Edited)
Photo of Ievgen Morskyi

Ievgen Morskyi

  • 4 Posts
  • 1 Reply Like
Does the word 'early' in Brian's)) 'early preview program' mean that aforementioned improvements are not coming in December update and we'll have to wait another couple of months for them ?
(Edited)
Photo of David Martin

David Martin

  • 16 Posts
  • 11 Reply Likes
Harken back to October 2015, when the geniuses at Adobe came out with that disastorus update which rendered Lightroom all but unuseable.  It took those idiots two (2) months to fix the import function, and they never fixed the memory leak and performance problems, which have only become worse, according to the reporting.

This release has far more issues—more than National Geographic!—and if it is fixed in 2017 it will be a miracle.  (I do not believe in miracles; only results!)

Your best bet is to not have upgraded in the first place, as I refused to do, or revert to the previous version—if you can.

Adobe Lightroom Classic is a World-class POS.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3946 Posts
  • 1362 Reply Likes
Ievgen, if you want access ASAP, sign up for the program. The fact they're testing their fix so carefully before releasing it to everyone is a GOOD thing!
Photo of Barry Young

Barry Young, Director of Engineering, Lightroom products

  • 53 Posts
  • 48 Reply Likes
Victoria, we can start with this initial wave and solicit a wider net if needed later. I think we're good for now though with the names I have received so far. 

Barry
Photo of Cat Chandler

Cat Chandler

  • 1 Post
  • 0 Reply Likes
I also am having a memory hogging issue with Lightroom - but I only use Lighroom CC. My problem is occuring when I have Lightroom open but am using other applications. Today I was monitoring it - It went up from using under 300mb of RAM, to around 1200mb, while I was doing nothing but streaming music and using eBay. This was in a half-hour time frame. I have to keep Task Manager open constantly to kill it in case it starts hogging all my memory - last time this happened, it crashed my computer. For reference, I have an i5 processor and 16GB of RAM - Lightroom and Photoshop are installed on an otherwise-empty SSD.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3496 Posts
  • 1101 Reply Likes
1200MB is nothing when you have 16GB to play with. It's probably syncing or doing other background tasks. Which Lightroom CC are you using? Lightroom CC 2015 that's been out for 2 1/2 years, or the new cloud-native Lightroom CC?
Photo of Robert Frost

Robert Frost

  • 371 Posts
  • 41 Reply Likes

As Victoria said, LR does all sorts of checking of the catalog, previews, previews database, etc when you are not using the program actively. When you are using it, it tries to speed things up by loading images that it thinks you might want next into memory. LR often uses 6-9Gb of my Ram, and  occasionally I've seen it use 12GB. No problem! That is what it and your OS are designed to do.

Bob frost

Photo of David Martin

David Martin

  • 16 Posts
  • 11 Reply Likes
Sorry Victoria and Robert, but you're missing the point. 

Lightroom CC 2015 AND Lightroom Classic CC are sequestering huge amounts of RAM when the application is doing nothing but sitting on the desktop open.  And it refuses to release the RAM unless one uses a utility such as Clean My Mac 3 or Memory Clean.

This is not a new problem, its been going on for at least two years, and it seems to become progressively worse as the catalog increases in size.  In software engineering we call this behavior memory leakage beyond what the basic operating system garbage collection (recovering of unused memory) function is capable of performing.  Mac systems, being based on Unix, have always been far better at garbage collection than Windows, but even High Sierra cannot cope with this memory hog sitting idle on our desltops.  (Bill Gates famously stated that Windows NT didn't need to perform garabge collection; developers should not allow memory leakage.  Clearly Adobe ignored Big Bill, which is understandable as there's been a hate-hate relationship between Microsoft and Adobe going back to the days of John Warnock and the Postscript/True Type font wars of the 1990s.)

LR CC 2015 can easily use 12GB of RAM on my MacBookPro Retina (16GB), which I use whilst on location or traveling.  On my MacPro, I recently swapped out the four (4) 16GB SIMMS for four (4) 32GB SIMMS, and LR CC 2015 wastes no time in grabbing 26GB.  However, the system does not have to resort to compressed memory or file swapping because that still over 100GB available.

But this is Adobe's fault.  They focus too much on gloaming on new, useless features for the selfie-stick crowd instead of reworking the database to a true releational database with high referential integrity and focusing on performance, multithreading, and multiple core processing which working professional require.

Couple this fundamental issue with the plethoria of bugs being reported in this forum, and you have a major release of Lightroom which is arguably worse than the October 2015 disaster, and this time around Adobe is doing absolutely not a damn thing about it!
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3774 Posts
  • 1249 Reply Likes
David,  I was replying to Cat, who reported a small RAM usage and wasn't clear on which version.

I'm not disputing that you're seeing a memory leak. I've seen massive memory usage in the past too, and traced that one back to sync. I'm sure there are other triggers too.
Photo of Kimmo Hansen

Kimmo Hansen

  • 1 Post
  • 2 Reply Likes
Well, the memory problem is still not solved in the latest update. LR Classic CC still drains all your computer memory, runs more and more slowly and finally crashes (develop module not responding) I must say that you managed to mess up this program pretty good and it seems to me that you need outside help to solve this problem and all the others for that matter. LR Classic CC is currently a mess and I am looking for alternative software.  
(Edited)
Photo of Barry Young

Barry Young, Director of Engineering, Lightroom products

  • 48 Posts
  • 40 Reply Likes
Hi Kimmo, we are still testing these changes internally before releasing publicly. Many people on this thread have joined our prerelease and are seeing positive early performance improvements. I can invite you to prerelease if you want to experience the improvements that will be coming. See my post above for my contact info. 

Regards,
Barry
Photo of Assaf Frank

Assaf Frank

  • 147 Posts
  • 44 Reply Likes
I can summarise the pre-release performance it in one word  A M A Z I N G.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3774 Posts
  • 1249 Reply Likes
> I can summarise the pre-release performance it in one word  A M A Z I N G.

Oh Assaf, I can't tell you how much that's made my day!!!
Photo of Assaf Frank

Assaf Frank

  • 147 Posts
  • 44 Reply Likes
you just got your 1000 Like :)
(Edited)
Photo of Assaf Frank

Assaf Frank

  • 147 Posts
  • 44 Reply Likes
It makes editing images a joy again. Instead of me waiting for Lightroom, Lightroom is now waiting for me.
Photo of Sven Kohle

Sven Kohle

  • 39 Posts
  • 17 Reply Likes
Hi, I was also suffering from severe performance degradations when upgraded to LR7.0. It became absolutely unusable after 10-20 min of use, CPU consumption incredibly high. I upgraded to LR7.1 yesterday and so far it improved a lot. I would say, perceived same performance than LR6 which is a good thing compared to LR7 speed. Still I don't see any improvements so far. (iMac late 2013 i5, 24GB, Nvidia)
Photo of Assaf Frank

Assaf Frank

  • 147 Posts
  • 45 Reply Likes
you should join the pre-release testing (7.2) it's even faster...
Photo of Barry Young

Barry Young, Director of Engineering, Lightroom products

  • 53 Posts
  • 48 Reply Likes
Hi folks, this is a reminder that the prerelease program is under NDA and should not be discussed in this public forum on get satisfaction. Please post your comments in the actual prerelease forum that you were invited to. Thank you.

Barry
Photo of martijn Saly

martijn Saly

  • 189 Posts
  • 13 Reply Likes
This problem has existed since at least Lightroom 5.0, all the way through to 6.14.
It's time this problem got solved once and for all. It's completely insane to have a bug like this stick around for that long. Even if it's really hard to track down, Adobe is a big company with big resources, and pouring in feature after feature while keeping a SEVERE performance bug in there, is unacceptable.
(Edited)
Photo of Emil Lenc

Emil Lenc

  • 2 Posts
  • 1 Reply Like
Does anyone know if the memory leak during syncing is supposed to be fixed in LR 7.2 classic? I just updated to 7.2 and the memory usage still sky-rockets while syncing with the cloud. I had to stop it when it was using more than 30GB because the laptop was becoming unresponsive. It's now 2 months since I was last able to run LR classic :-(