Skip to main content
Adobe Photoshop Family

580 Messages

 • 

12.1K Points

Mon, Jun 13, 2016 11:39 AM

Lightroom 2015.6 Extremely Slow

I am not sure if this is the best place to post this but I am extremely frustrated! This version is extremely slower than the previous version, which in turn was slower than the one before it. Moving from one image to the next, takes at least 5seconds and adjusting any slider causes Lightroom to freeze, with the lovely "circle of death" reminding me that it's thinking and I should not perform any actions, for 2 seconds or so. I am a very tolerant person but feel like I've had it now! It feels like I am falling out of love with a craft that I once was excited about because editing, which is a very important part of the process, doesn't work. And instead of improving, Lightroom has quickly gotten worse over time! It has taken me 2 and a half days to edit 450 photos, and there's a few more to do but Lightroom has now CRASHED hence my angst here! I have a couple jobs more to edit and I am in a position where I am not seeking after more work because of a backlog of jobs to edit. This is really costing me and I am very angry because I just want to get on with my work. Yes I have a decent system, yes I have plenty of RAM, yes I have a SSD installed. ADOBE, please please please, I just want to edit and enjoy it.

Responses

87 Messages

 • 

1.6K Points

4 years ago

Same to me. OK, not that worse, but it feels way slower than previous version or even 2015.1 or .2.

82 Messages

 • 

1.3K Points

4 years ago

The crash is maybe because of a memory leak (I think) I observed. Need more data to collect and send them. As for the rest, I am just like you. :-(

580 Messages

 • 

12.1K Points

4 years ago

I rarely post problems because I always think someone would have already posted about my issue. I just couldn't help myself here. It's that bad! The numbers and stats I've listed are precise btw!! Man, I hope they look into it.. I'm pulling my locks out here ha!

1 Message

 • 

62 Points

I agree this is really driving me crazy - Lightroom keeps stopping everytime I move a slider or switch to a new image.  My work is getting further behind and I have about 30 shoots to finish - arggggggg - Come one Adobe give us back the previous version at least it didn't keep stopping.

87 Messages

 • 

1.6K Points

Gwen, then do this. It takes you 10 minutes and after that you're much happier:

https://helpx.adobe.com/lightroom/kb/roll-back-to-prior-update.html

39 Messages

 • 

1.1K Points

4 years ago

U're not alone. Lr is slower and slower. On my 6-core/32GB/3x ssd computer Lr is always slow. 
One option you have is to DISABLE "lens correction" and "detail" panel. Especially later, because noise reduction, which Lr calculates at every "develop slider" change, really slows things down. 

But it is upside down worklflow and U must turn it image per image (times 450 images), and later again switch panels on, image per image (times 450). 

It definitely helps, but it is another pain to do it. 

Adobe should (no, Adobe MUST) provide global turn on/off of panels. Several smart(er) software (or Premiere plugins) have this function built in, so U can disable rendering effect until restart/or export. 

Hope it helps. 

580 Messages

 • 

12.1K Points

I will try that Mihael, - turn it off image by image? Wow! Umm I will try that but Adobe should really sort this. Thanks for your reply

82 Messages

 • 

1.3K Points

I say OK. And yet total nonsense. To turn off features in order to kick the old bucket running!?!

Champion

 • 

5.9K Messages

 • 

104K Points

That shouldn't be necessary. Adobe would much rather figure out why it's that slow for you and not for most users. The more information you can provide on system specs, monitor resolution and graphics card (& its driver version), camera type, timings, etc, the more likely they are to find the pattern.

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

53 Messages

 • 

926 Points

I appreciate Victoria, if Adobe would fix this. But I do not know user that would say Lr is fast. I tried C1 - it have a lot of shortcoming too, but it is not as stammeing as Lr when loading image ir moving sliders. I use Lr from Version 1,5... never was fast. As computers goes faster, images grow in size, so relatively we are the same after decades. And I have everything on SSD's, separate for system, Lr catalog and cache (12GB), and images, than GTX770 card, 32GB 2133 ram, 6-core cpu... and I wait for sliders... not (so much) if I disable NR and sharpening and lens distortion. But still... I remember now defunct CINEFORM FIRST LIGHT software - RT as it can be - for video. Yes we like Adobe integration, but we pay it hard every day. I must say that I search elsewhere for alternative. But Adobe won this buying all relevant products in the past. 

39 Messages

 • 

1.1K Points

I have 99 GB of cache now. Maybe it is slightly more fluent..

39 Messages

 • 

1.1K Points

4 years ago

... some say you enlarge Lightroom CACHE to some odd large figure, like 20GB... I did it to 13 GB (as my space allows), but I cant swear by it helps much. Disabling panels, does. 

87 Messages

 • 

1.6K Points

4 years ago

That doesn't help. LR CC 2015.6 is slower than 2015.5.1.

(Cache is 50 GB here, always a new catalog for each project. Everything is most possible optimized. Logically the solution can't be to optimize here and there (noisereduction off, etc), because it worked better before 2015.6.)

580 Messages

 • 

12.1K Points

Agree on this, mine is even larger(90GB) and I've never seen an improvement. I'm also optimised out!

82 Messages

 • 

1.3K Points

So is mine. (88 GB).

Nothing.

Build 1:1, running both catalog and DNG files doesn't improves local adjustment and spot removal at all. Neither is my video card which btw is almost unused the whole time. :-(

87 Messages

 • 

1.6K Points

4 years ago

Hups, please try this:
Stop LR, Start LR, be happy with the speed. :)

OK... Why i'm telling that: Had a Baby here two hours ago and made the preview for the clients. It took me 30 minutes (!) for just 220 pictures from Canon 5D3 for the 1:1-Preview. Switching from one picture to another was a pain in the a.... So unbelievable slow. Note: Nothing has changed since generation of the preview, the Cache is 50 Gig, RAM is 32 Gig, newest Intel 8-Core at 4GHz. Slower than usual.
Than i stopped LR, did something else, started LR with another catalogue and it is fast! Hmmm...
Normally i'm browsing through the pictures right after having done the Preview. And that was fast. OK, somewhat fast. Now it's annoying slow.
Maybe we have to restart LR after generating the Cat and the Preview?

87 Messages

 • 

1.6K Points

Addition: RAM-Usage was around 15 Gigs for all while it was unbelievable slow.
Now RAM-Usage overall (for the System) is something around 6 to 9 Gigs. Hmmm...

87 Messages

 • 

1.6K Points

2nd Addition.
RAM-Usage goes up again to 15 Gigs and LR slows down. But not that dramatic way.
Minimizing (not closing) LR and the Usage goes down to 7 to 8 Gigs.
Maximing LR and it runs again fast.
Memory Leak?

39 Messages

 • 

1.1K Points

Yes after time of usage Lr become "clogged" up and restart helps wastly. But that was with small cache. In 99 GB of cache that is not the case any moore. But unfortunatelky we are talking of it's natural slowness, not extra slowness when cache is full. 

Adobe Administrator

 • 

8.6K Messages

 • 

122.3K Points

4 years ago

Jerry,

I would recommend the following:

1. Reset your preferences file by closing Lightroom, holding down [Alt/Opt]+[Shift] and relaunching Lightroom. Overwrite the preference file when requested. 
2. After preference reset, uninstall Lightroom from the Creative Cloud App.
3. Reboot.
4. Install Lightroom via the Creative Cloud App. 
5. After installation, Optimize the catalog first thing. 

Does you performance/stability improve now?
Adobe Photography Products

Quality Engineering - Customer Advocacy

150 Messages

 • 

2.9K Points

can't be certain that I can see improvement, but thank you for the tip.

the plugins - if there were located in the modules folder
C:\Users\User\AppData\Roaming\Adobe\Lightroom\Modules
they lasted the reset other wise the didn't so I have moved them to that folder and they came back.

important point about spot removal which is an issue with the last version as well.
1. I'm aware of the GPU acceleration issue - that it works faster without it.
2. I found that the main problem of slowness by far is the 4K resolution
3. for example if I do spot removal on 4k on big panoramas of 40000x7000 pixels (280MP) it takes about 8 seconds between each spot removal click to until I get my mouse control back (this includes black screen flicking back and forth). GPU acceleration off., with GPU Acceleration on its about 13 seconds for each spot removal click, and the detail tab is switched off (noise removal).
4. now the best part is that once I switch to 1920x1080 it is instant yes !! on the same massive file.
5. my spec is Nvida GTX 980 Ti, i7 5960X 8 core 64GB DDR4 everything is on m.2 PCI EXpress NVME and SSDs 
6. my files are Phase one IQ280 - 80MP
7. The slowness is in everything but mostly in spot or local adjustments functions (with the GPU off) the when I do sliders adjustment WB / Exposure I turn the GPU back on and its relatively ok in 4K but in 1920x1080 its super fast.

I have the latest drives from nvidia.

any suggestion will be welcomed.

1 Message

 • 

82 Points

This corrected the issues I have been having since the most recent update. Thank you.

22 Messages

 • 

446 Points

4 years ago

Hi @Rikk,
If we do this procedure (uninstalling and reinstalling Lightroom CC 2016), will we loose any personalised settings and configurations?
I'm willing to try.
Thanks,
Kostadin

Adobe Administrator

 • 

8.6K Messages

 • 

122.3K Points

4 years ago

A backup is always prudent.

Your catalog and user-defined settings should remain intact. 
Adobe Photography Products

Quality Engineering - Customer Advocacy

150 Messages

 • 

2.9K Points

I presume I will need to reinstall all the plugins?

Adobe Administrator

 • 

8.6K Messages

 • 

122.3K Points

Normally, no. They should come along for the ride. 
Adobe Photography Products

Quality Engineering - Customer Advocacy

22 Messages

 • 

438 Points

4 years ago

After using this version for a couple days now, I’m finding it significantly slower (painfully so) than the previous version. Turning off “Use Graphics Processor” seems to help. As soon as I have some time, I'll also try the advice provided above.

150 Messages

 • 

2.9K Points

4k display?

Champion

 • 

5.9K Messages

 • 

104K Points

4 years ago

Those of you who are seeing new performance issues in 6.6, can you keep your eye on Activity Monitor and see what the RAM usage is like when it's going slowly? I've seen it ramp up the RAM use to crazy levels twice, but I haven't managed to figure out how to trigger it yet.

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

87 Messages

 • 

1.6K Points

Look at my comments 5 hours ago.

Champion

 • 

5.9K Messages

 • 

104K Points

That's what triggered the thought Stefan. I'd love to know if others are noticing the same... and if you are, is sync on and what are you doing before the memory starts to rise?  I've only seen it twice in some weeks of usage, so is it occasional or all the time for you?

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

87 Messages

 • 

1.6K Points

OK, what i was doing before... Everything. :)
I notived that behaviour with the RAM yesterday for the first time.
What i did before:
- Imported around 200 RAWs, automatically applied a preset and keywords, 1:1-Preview-Generating and then Rating the Pictures at 100%. Nothing else. Saw the RAM-Usage of 16 Gig (i have 32 of them)
- After restart RAM-Usage was ok. Then rated the Pictures and nothing else. RAM-Usage goes up.
- Another restart and just adjusting the exposure and uprighting and cropping. RAM-Usage goes up.

Seems that from Picture to Picture RAM-Usage goes up. And yesterday it was just a question of time. Today i will continue to edit 2 weddings and will have an eye on what happens...

6 Messages

 • 

174 Points

Exactly what I am seeing - moving from picture to picture in Develop - scrolling along the thumbnails at the bottom takes my LR2015.6 from a start of 2GB in Task Mgr (win10)  up to 6 or 7GB without doing any adjustments.  With adjustments it gets to 11GB and then becomes too slow.  A restart takes it to back to 2GB then it builds again.  I'm restarting LR every 10-15 minutes. Poor...

87 Messages

 • 

1.6K Points

It seems that there's no need for restarting LR. Just minimize, waiting 2 seconds, maximize and it's working again. Try it!

8 Messages

 • 

190 Points

I have a dual xeon x5690 with 96GB of RAM, SSD drive with 200GB dedicated for cache and LR is utilizing 20% of the RAM and crawling like it's used 100% of the resources.  I tried to render 1:1 previews earlier today and it was taking hours.  It's brought a more than capable system of accomplishing mundane tasks like simple exposure corrections for a wedding to a grinding halt.  I should have been finished with this wedding hours ago!

Adobe should NOT be rolling out versions with bugs this large such as memory leaks crippling systems, what happened to beta testing products like the old days?!?

I'm rolling back to a prior version but this is beyond ridiculous!

15 Messages

 • 

434 Points

same with me, it has brought my work to a halt

26 Messages

 • 

350 Points

Hello

What size previews are you making and have you considered making much smaller ones to see if things are better? There is most probably a big problem with Lightroom and larger size previews. If you have 1920x 1200 previews as I use, I have few problems, 1:1 zoom in 5 or 6s and a similar time to create them.

MDE

137 Messages

 • 

2K Points

Well 5 or 6 secs for 1:1 view is still a very mediocre performance, don't you think ? It just allows to work but not with great pleasure.

8 Messages

 • 

190 Points

I usually build my previews when I take a break for a catalog, I photograph a lot of weddings so between working on editing a catalog I'll build the previews for another while at lunch or something so not to interrupt my editing.  Every second counts when editing large volumes and can equate to 10-30 minutes of extra time gained daily so over time that scales rapidly.

While my Quadro 6000 graphics card is not the newest kid on the block its not exactly a slouch with 6gb of ram.  enabling the graphics processor with the latest release results in the LR edit pane blacking out for several seconds before refreshing.

Because LR holds on to so much RAM and I have 96GB it takes more than a few seconds of shutting down LR before it restarts, I've just been using the restart LR feature beneath the enable/disable GFX card in the preferences.  This is faster, and I say that with a grain of salt than just closing LR and re-opening the catalog.

I'm really pissed at Adobe at the moment.  Come out with an easy rollback till they can get this fixed, I tried though not very hard to rollback to a prior version and was not successful, Creative Cloud Panel fought me the entire time.

26 Messages

 • 

350 Points

Hello

Well it is a 6 year old computer with 16gb of ram and slow at it might be, it works!

It is not a problem, it is just my hobby. I can also do a lot of cloning, slow as it is

MDE



26 Messages

 • 

350 Points

Hello

As a postscript, there is a colour difference between the two, as the top is an export and the bottom a screen grab.

MDE

26 Messages

 • 

350 Points

Hello jeckylproductions

You still have not said what size previews you are using. It might be very important to give Adobe a clue. Have you tried much smaller previews like 1440, just as a test. Make a test folder with 50 images and try smaller previews till you get an acceptable performance.

There is obviously something seriously wrong with how Lightroom works on some computers.

MDE

8 Messages

 • 

190 Points

Hey Mike, thanks for asking, I mentioned I was rendering them at 2048 in another area of this thread but forgot to here.  Regardless of rendering 1:1 previews, even when it is not rendering previews it is leaking memory.  I can remain on one image and move my mouse across the image and watch in the resource monitor the memory use increase, this does not change unless I close or minimize LR.

I'd say forget about the 1:1 rendering as an issue, I think as a whole their is an issue with memory, cpu and GFX card usage in this version.  Their is a problem with the build overall, I thought I waited long enough before installing 2015.6 and it's release, obviously not.

I'd just prefer to rollback if someone has a walk though or link for that?

26 Messages

 • 

350 Points

Hello

Thanks for the reply.

2048 is not very large for a preview, I use 1920x1200.

I don't generally use GPU. In my system the GPU makes panning at 1:1 quite smooth, but the actual redraw is slower. Also all the sliders are really notchy and results in an overshoot.

Without GPU panning can be smooth, but mostly very notchy and clicking on another image can take quite a long time to change whilst panning. The sliders are smooth and there is no overshoot. This pretty well the same behaviour for all the versions of Lightroom 6, but 6.6 is slightly worse.

I don't have CC so I can just go to the Adobe site and download older versions. I have not gone back to 5.7, even though I have it. The GPU would not work with 5.7

https://helpx.adobe.com/lightroom/kb/lightroom-downloads.html

This links to previous versions of Lightroom

MDE





26 Messages

 • 

350 Points

Hello

I have started this topic, you might be interested in

https://feedback.photoshop.com/photoshop_family/topics/why-does-lightroom-use-so-many-resources/edit

There seems to be a lot of problems concerning the performance of Lightroom 6.6

At the moment I am on Lightroom 6.5 standalone.

I use Win 7 pro on a 6 year old i7 870 Quadcore with 16gb of ram, a Samsung SSD and a AMD 5450 video card

I have just done a small experiment.

With just Windows running the resource monitor shows that the ram in use is 2354mb

I created a new catalogue on the SSD. Cache 100gb, video cache 10gb

The ram in use went to 2633mb

I added one Canon 5D3 image to the catalogue and created a 1920x1200 preview with high

quality.

The ram in use with no edits went to 3585mb

Now the 1920x1200 preview at 16bit should be about 13mb

So why has the addition of just one image to the catalogue increased ram usage by 952mb

Using Develop and no edits I zoomed 100% and panned the image about.

This was smooth, but the ram usage went to 4371mb, an increase of another 786mb.

This one image takes up 1738mb

Now I did some edits in exposure, clarity, vibrance, lens profile and auto upright, zoom to 100% and panned again.

Ram use went to 4606mb, up another 235mb.

That is a total of nearly 2000mb for one 13mb image.

Now I added 7 100,75,100 clones, zoomed 1:1 and repeated the panning.

No GPU the panning was very smooth and redraw was pretty instant and no CPU thrashing, which happens in my normal catalogue.  

Ram uses goes up to 4919mb

That is with cloning and the above processing, ram use for one 13mb image is 2286mb.

This the memory usage in Sys info

Built-in memory: 16374.1 MB
Real memory available to Lightroom: 16374.1 MB
Real memory used by Lightroom: 1902.2 MB (11.6%)
Virtual memory used by Lightroom: 1947.2 MB
Memory cache size: 276.3 MB

Quite amazing.

MDE

Employee

 • 

1.7K Messages

 • 

32.4K Points

Depends on your RAM availability, Lightroom caches a few of the last loaded negatives in the RAM just in case you might do something with it (develop it or walking back and forth between two photos etc) in the next moment. Lightroom wants to keep it available just in case. It is not he JPEG previews that took up the RAM.

Principal Scientist, Adobe Lightroom

13 Messages

 • 

288 Points

4 years ago

I'm pretty much in the same boat as the OP. Latest LR update has made it pretty much unusable. For me, it's CPU not Memory. My CPU gets pegged any time I try to make any adjustments in develop module. A simple adjustment of say highlights causes the CPU to spike and it takes 3-4 seconds to recover and be able to do anything else again. Just switching from develop to library module takes 5+ seconds. It's very frustrating and making me seriously consider trying out Capture One Pro since I can't afford to be impacted like this with one of the major tools of my workflow. Didn't have any of these issues prior to the update a few days ago.

Champion

 • 

5.9K Messages

 • 

104K Points

What are your system specs David?  Processor, RAM, graphics card and driver version, monitor resolution, calibration software even (there was a case a while back with performance problems related to the monitor profile...) and camera model and file type?  And what kind of adjustments have you applied... does it take as long at default settings?

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

13 Messages

 • 

288 Points

I'm not at my computer right now but it's a late 2014 iMac 27" Retina, 3.3ghz Intel Core i5, 24GB RAM, etc. My system specs haven't changed in over 6 months. These issues just started after I upgraded LR a few days ago. 

Champion

 • 

5.9K Messages

 • 

104K Points

When you get back to the computer, just try pausing Sync and see if that helps. Some people are reporting LR 2015.6 syncing their photos and I've seen that cause major performance issues at times.

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

Champion

 • 

5.9K Messages

 • 

104K Points

Oh, and also check whether the GPU is enabled in Preferences or not.

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

13 Messages

 • 

288 Points

Thanks for the suggestions. GPU is definitely enabled. I've heard some folks recommending to turn that off but that's supposed to be a good thing to offload work from the CPU to a GPU, no?  Not sure what you mean by sync - is that syncing between desktop and mobile? I've never used that and have never even logged into LR mobile before.

Champion

 • 

5.9K Messages

 • 

104K Points

Correct, GPU is most useful on high resolution screens like the retina iMacs. On some machines with older GPU's, it can be better to turn it off, but that won't hold true in your case.

Sync - yes, syncing from desktop to cloud in this case.  Click on the Activity Center, top left, and also see if Face Recognition and Map Locations are enabled or not.  (You should be able to leave them all enabled, but we're just trying to narrow down the cause of the issues.)

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

87 Messages

 • 

1.6K Points

It has nothing to do with Cloud, Face Recognition, GPS, GPU, ... (All disabled here together with newest drivers and GTX970 as GPU, 32 GB RAM, powerful CPU.)

13 Messages

 • 

288 Points

I confirmed that Sync, Map Locations and Face Recognition are all off.

82 Messages

 • 

1.3K Points

4 years ago

Here is my data. PLS note this is only LR currently running. Within those 10 min. I was processing images within LR only.



I can provide much more data if needed. What you see is only LR process running. I have a descent control on my win background processes and always throw an eye on my Process Explorer which is running always with admin rights. 

PS: And for some stupid reason I am hovering the two types of memory (instead of only the one). Sorry.

But never-the-less the beside the error still the trend of memory leak can be observed.

Champion

 • 

5.9K Messages

 • 

104K Points

Interesting indeed. Were you active on the machine at the time?  What had you been doing?

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

82 Messages

 • 

1.3K Points

Processing Canon's 5Ds 50 MPx files, which already were converted to DNG files on a small catalog (both files and pics on SSD) while sitting on my Win 10x64, LR 6.6, 32 GB RAM, i7-6700K computer with Palit GTX 970.

Champion

 • 

5.9K Messages

 • 

104K Points

Thanks. Does it continue to climb to crazy levels if you leave it running?

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

22 Messages

 • 

446 Points

On my machine the amount of RAM used by LR can (sometimes) grow up to 99% ot the total RAM (64GB in my case, iMac 5K, 27", late 2015, 4GHz i7, AMD Radeon 4GB Video, 1GB SSD). Happened on previous versions of LR too. I noticed that performance deteriorates faster and worse when Safari + Mail are both open as well. If I keep them closed, LR takes much longer to deteriorate (like 1h) until a close and reopen os needed.

Champion

 • 

2.2K Messages

 • 

37.4K Points

I can confirm the memory leak. I believe it's due to the change in 6.6 to that caches the Develop module previews for the image files adjacent to the currently selected file (i.e. 3 previews). Simply "browsing" images in the Develop module cause memory usage to climb and not be released. Use of the Adjustment Brush on multiple images is even worse. See this post: https://forums.adobe.com/message/8812806#8812806

6 Messages

 • 

174 Points

4 years ago

I'm also seeing my screen go black apart from the labels I have at the top of the image (exposure details etc) and then it comes back after up to 5 seconds.  Hasn't crashed yet - but feels like it will. 


Doesn't Adobe test these updates on a broader user base before releasing them?

Champion

 • 

5.9K Messages

 • 

104K Points

Yes, there is prerelease testing. It seems there is a very specific set of circumstances triggering this issue, otherwise there would uproar by now.  Even now, there are only a few of us in this thread that have ever seen this issue, and I spent days trying to figure out how to trigger it.

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

87 Messages

 • 

1.6K Points

I'm an Admin in a german LR-Facebook-Group. There are a lot of others having that problem. Don't look just at us few here...
It seems to be triggered by everything. Switching to the next image. Doing with the heal brush. Looks like a memory leak in general.

Champion

 • 

5.9K Messages

 • 

104K Points

Great, see if you can get them to post on this thread. The more information the engineers have, the quicker they'll be able to spot a pattern and fix it.

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

87 Messages

 • 

1.6K Points

I already tried that for two issues (slow and not remembering import-location) but... Only two people did that. :(
Maybe most of them are not doing that because they're not used in writing in english language.

Champion

 • 

5.9K Messages

 • 

104K Points

Feel free to tell them to post in German and we'll Google Translate it.

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

87 Messages

 • 

1.6K Points

Done. Let's see if anything happens.

6 Messages

 • 

174 Points

Are we at an "uproar" point yet?

137 Messages

 • 

2K Points

Well I see those black screens too, then normal operations seem to resume after a few seconds.

1 Message

 • 

60 Points

black screens too

8 Messages

 • 

190 Points

Uninstalled and reinstalled CC 2015.5.1. It is running again without memory leaks or performance issues. I'll wait until a new patch comes out before testing the waters again.