Lightroom Classic 8.0: Almost unusable with multiple problems

  • 3
  • Problem
  • Updated 2 days ago
  • (Edited)
Multiple issues since update to LR Classic CC 8.0.

I updated when the update was released - I have a Fuji X-T3 and was happy to see new camera support added.

Since then, LR is so slow as to be almost unusable:

- when switching between Library and Develop mode, screen often goes white
- histogram takes a long time to appear, and often says "calculating"
- LR needs to be force closed repeatedly because it will not respond (and it slows down the entire computer)
- CPU consumption spikes erratically when LR is open, with LR going from approximately 5-90%, even when open and idle


I contacted Adobe for support via chat (and subsequent remote control). Case # 
ADB-4164592-M8L1 . After almost an hour of troubleshooting, agent told me that 8.0 had known issues and to roll back. I don't want to do this because I want the X-T3 support. Agent tried clearing cache and video cache. Each time, the cache would not clear and LR had to be force killed.

I also took the following steps, as suggested by an Adobe Digital Imaging Advocate, to no avail:
Close Lightroom
Restart the computer
Use the Adobe Creative Cloud App to uninstall Lightroom Classic CC
Restart the computer
Install Lightroom Classic CC via the Creative Cloud App
Restart the computer
Launch Lightroom
Wait 5 minutes

I need some help here , please.
Photo of giseled

giseled

  • 30 Posts
  • 0 Reply Likes
  • frustrated

Posted 3 weeks ago

  • 3
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4277 Posts
  • 814 Reply Likes
Greetings giseled,

I am sorry for the issues you are having. Are you using a Mac or Windows machine. What is your OS version? 
Photo of giseled

giseled

  • 30 Posts
  • 0 Reply Likes
I'm on a MacBook Pro, running High Sierra 10.13.6, with a 3G Core i7 processor and 16GB Ram 
Photo of dmeephd

dmeephd

  • 222 Posts
  • 50 Reply Likes
Without knowing what OS you're using, no one can be definitive.  However, I run LR8 on a MacPro with Mojave and 128GB of RAM.  I find that LR8 will gobble up 95GB of RAM whilst doing an Import/Preview Build which shows no progress.  I have to frequently use Clean MY Mac X to release the memory and get LR8 to go back to work.

If it wasn't for Loupedeck+ I would go back to LR6.  LR7.5 to LR8 have been a huge disappointment as far as performance is concerned.
Photo of giseled

giseled

  • 30 Posts
  • 0 Reply Likes

Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4277 Posts
  • 814 Reply Likes
Giseled,

I don't see a preference file mentioned:

A Preference File will survive a Lightroom uninstall/reinstall. Sometimes weird behavior is corrected/cured by resetting the preferences. 

Reset Procedure:

1. Close Lightroom.
2. Hold down [Alt/Opt]+[Shift] while restarting Lightroom. 
3. Overwrite the Preferences when prompted by the dialog.
4. Close Lightroom.
5. Restart Lightroom.

Does the behavior continue after resetting the preferences?
Photo of giseled

giseled

  • 30 Posts
  • 0 Reply Likes
I'm out of disc space, so something has to go
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4277 Posts
  • 814 Reply Likes
If you aren't actively using Smart Previews, those can be regenerated again if you need them. That would free up a big chunk.  
Photo of TangCanada

TangCanada

  • 87 Posts
  • 42 Reply Likes
This one catalog nonsense that all the Adobe reps like to preach just does not make sense in real life. Then everytime you upgrade LR the whole catalog has to be updated, result is multiple bloated catalogs with same pics from years ago.

I use separate catalog in its own folder for each shoot and when done I can easily pick up the whole folder with originals etc and dump on external drive to free up space.
Photo of giseled

giseled

  • 30 Posts
  • 0 Reply Likes
I rebuilt all of the previews (246 failed to build) and it's still a mess. I also deleted old catalogs. I've spent about 10 hours on this so far (not including time to build the previews again, which was over 24 hours). To say I am annoyed is an understatement.

I echo the sentiments of others - these releases are poorly tested and are trending in the wrong direction. 
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4277 Posts
  • 814 Reply Likes
What was the error message you saw on the 246? Did you happen to screen shot it?
Photo of Andy Hewitt

Andy Hewitt

  • 73 Posts
  • 12 Reply Likes
Looks like this is linked to the issues I'm having after clearing some caches. Perhaps it's not that after all.

I too am suffering with huge amounts of RAM usage, and completely slowing to a halt.

I have tried resetting preferences and rebuilding syncing data, but without any success.

Today I left Lightroom Classic running on my Mac (running Mojave) while I was at work, but with syncing paused, and I still found it had frozen, and using more RAM than I have installed. I hadn't even applied any edits or anything like that.

Looks like a massive runaway memory leak or something.

Cheers,

Andy.
Photo of dmeephd

dmeephd

  • 216 Posts
  • 50 Reply Likes
Lightroom has almost always had some issues with memory leaks, but with LR7 and LR8, it has become far worse, beyond the ability of Mac OS X to accomodate through its standard 'garbage collections' processes.  (Windoze does not have this facility as Bill Gates said it was never necessary.)

I too can leave LR8 doing nothing, not even writing to XMP files in the background, and by morning it will have gobbled up as much as 95-98GB.

When it's working, I have to clear memory in order to get LR to come out of its stall.  Memory Clean will oft times notify me that "Lightroom is inactive and you can clear nnGB of memory by stopping it" where nn is lots of RAM.

Poor programming effort by Adobe.
(Edited)
Photo of Andy Hewitt

Andy Hewitt

  • 73 Posts
  • 12 Reply Likes
Pretty much unusable now. Every time I leave it dormant, I come back to find it consuming increasing amounts of RAM, and beach balling. It can be quit, if you can wait many, many minutes for a menu to appear, or for Command-Q to work. Force-Quit usually works OK quite quickly.

So far now I have tried:
Rebuilding Syncing Data
Resetting Preferences
Uninstalling and reinstalling Lightroom.

I'm very reluctant to try deleting CC web data, as the problem occurs even with syncing paused, so I think this is more a localised problem.

Performance should not be an issue, my system isn't new, but is no slouch either:
Apple iMac (Late 2013) 27" 3.2GHz Quad Core, Nvidia GeForce GT755M 1GB, Crucial 500GB SSD (250GB free) where the catalogue is. My photo originals are on an external 3TB HDD (partitioned to 1.3TB for the photo storage) connected by FW800. GPU Support is ON.

Until the last few weeks this has proven to be a very well performing setup for editing and managing my photos, and I have rarely, if ever, noticed any of the lags that others have found with more powerful, or newer, hardware.

The issue is occurring with Lightroom running, but idle (even in this state it continues to eat up more and more memory), so there is a very bad problem somewhere.
Photo of dmeephd

dmeephd

  • 216 Posts
  • 50 Reply Likes
Agreed.  I have these issues and I don't sync anything to the Cloud any longer (and even then, it was only a single folder of favorites to show clients, friends, and models my portfolio.)

GPU support can be ON or OFF, machts nicht.  I can have LR open on a monitor, be working elsewhere, come over to LR, and be greeted by the rotating beachball.  Infuriating!

The so-called Holy Grail of resetting LR preferences make no never mind.  LR 7 and LR8 are memory hogs...pure and simple.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4277 Posts
  • 814 Reply Likes
Andy, I would love a few screen grabs of your Activity Monitor - say 5 minutes after launch, an hour after launch and then one from a long idle period if possible.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4277 Posts
  • 814 Reply Likes
You are consuming a lot less memory than Andy so I suspect your two issues are unrelated. He gets to 28 GB and becomes non-responsive.  You are getting to a non-responsive state much more quickly. 
Photo of Andy Hewitt

Andy Hewitt

  • 73 Posts
  • 12 Reply Likes
Hi Rikk,

I've only been rebuilding the sync data in a desperate attempt to see if I can fix this. Rebuilding does seem to temporarily improve things for a short time. It very quickly syncs the bulk of images in my collections.

I've just tried it with syncing paused, and it stayed steady at around 980MB of memory usage. However, I did try that a few days ago, and I still got the rampant memory problem.

I do seem to be getting syncing stuck on a certain number of images each time though. Currently around 6,900 that are re-syncing (although nothing should actually need syncing). Each time I try the rebuild the number goes down slightly.

When I pause syncing, the sync system settles down to show no errors, and all images selected for syncing are showing as synced. No errors show on the Web CC either. As soon as I activate syncing, then the errors counter goes up, the All Synced counter goes down, and the 'Syncing xxx photos' goes up and down.

Of course I have tried just leaving it to work the issue, but eventually stalls when it get to the 'unresponsive' state. It doesn't seem to have actually crashed though, as with a little patience, it does eventually carry on working, albeit very very slowly.

And, yes, I've tried with and without the security software I'm running.

Quite a puzzle this one.

[edit] Just an update, I've just run Lightroom Classic and paused Sync, and it's had a really bad rampant memory consumption, jumping from 10GB to 16GB in 2-3 minutes.

Pretty much unusable right now.
(Edited)
Photo of Andy Hewitt

Andy Hewitt

  • 73 Posts
  • 12 Reply Likes
Just an update Rikk.

I think I might have solved my rampant memory usage with Lightroom. I had TechTool Pro installed, which is supposed to be reasonably OK with Mojave, although a full update is due soon. I uninstalled it and now that part of Lightroom's issues seems too be resolved. I'm seeing RAM usage around 2-5GB depending on what it's doing.

I have also been able to complete syncing now, but it was still a slow and painful process with much work to do to finish off the layout I had. Even after it settled down, I was left with nearly 2,000 images in the Errors section. Clicking on each one appeared to allow it to re-sync - but that was going to take forever that way, and selecting all did not seem to do anything. So, I cleared the sync errors, which has removed them from the synced collections.

After all the mucking about, I now have a shed load of loose albums in CC, which all need reorganising back into their folders. We really really need to have syncing of collections and folders enabled, that would help an awful lot.

Overall though (I know, probably not relevant to this thread, but I just want to vent a little), I have to say that I am getting more and more frustrated with using Lightroom. I seem to continuously battling against syncing problems, and various bugs, or simply stuff that just isn't right (thinking about poor colours with certain Profiles, and also with the new Process 5).

If I were a professional photographer, I would be a bit more than frustrated. The CC system does not feel robust enough to anything serious, if even a hobby user can stumble on issues too often.

Anyway, I thank you for your time and effort, you are always gracious and helpful.

Regards

Andy.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4277 Posts
  • 814 Reply Likes
Andy, good to hear the memory usage is under control again. 

I will pass along your syncing comments to the Classic team. 
Photo of Andy Hewitt

Andy Hewitt

  • 73 Posts
  • 12 Reply Likes
Thanks Rikk,

Syncing took a bit longer to sort. They were stuck on 1996 left for a long time, then eventually it all cleared. After that I had a count discrepancy between CC and Classic. After a bit more mucking about with logging out and back in, and yet another sync data rebuild, I finally managed to get all my synced images singing off the same hymn sheet.

Regards.
Photo of giseled

giseled

  • 30 Posts
  • 0 Reply Likes
I've completed all troubleshooting steps and nothing is working. Rikki - can you please work with me some more or have this issue escalated? 
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4262 Posts
  • 812 Reply Likes
I've contacted you directly.