Lightroom grinds to a halt after 20 mins use

Soldato
Joined
7 Aug 2004
Posts
11,158
As title, using very latest 6.6.1, no matter what I try, clearing the cache, editing off all SSD's, setting larger cache, rendering 1:1 on import, edit 10mp or 22mp images............ after about 20 mins it goes from nippy editing of each image, then hop to the next image, edit, etc..........then just grinds to a halt, it then takes about 5 seconds to change images and several seconds to make any alteration to the image :(

It's my full time job and I have a lot to get through & I have no idea why its doing this now, the only fix is exit, reboot PC and launch and go again :/

ANY ideas folks ?

Specs are very high end all running off SSD (install, image data, cache, separate SSD's)

Intel 4930k @ 4.6ghz
1866mhz DDR3 32gb
980TI x2
Various Samsung 850 EVO's
6TB Toshiba long term storage drive
Running on my dell 3008WFP 2560x1600
Spyder 5 Elite
Windows 10 Pro 64 bit
 
Last edited:
I had the same problem with 6.6 until they released the minor upgrade which seemed to help a lot. I think there is still a memory leak there somewhere which is causing the program to consume more memory than needed. Have you tried switching off GPU acceleration, as I found this made the workflow of quickly editing images much more slick, as it's not transferring images into the GPU memory for manipulation first before you can edit them.

The other trick to try instead of rebooting is simply to minimise LR to the task bar for 10-20 seconds which allows LR to tidy up the memory a bit and performance improves, but then to do this every so often before it gets too bad.

Bizarrely, I was editing a batch of photos in reverse, it latest image first moving back towards the earliest, and alarm ran out of memory and I had to reboot. Not had that since as I've been working through from earliest first for the last few batches.

I also have a separate catalogue for each batch of photos.
 
Interesting!!

Thanks very much will look into that - yeah tried without GPU and its *frustratingly* slow, but still quicker I suppose than when it starts slowing down, will give it a longer go.

Also a new catalogue for each batch ? :O do you mean every shoot you do ? :O

My catalogue is a few years old now, around 9.7gb in size unpacked, I suppose I could start a new one but not sure how feasible that would be, Id have to work out which set of weddings to kick off a new one - but for me id need at least 10 weddings or more in one catalogue, just 1 isn't particularly practical.
 
Yes, I do lots of motorsport photography with anywhere between 1000 and 4000 images per event if it's a Sat/Sun event. I copy all the files from the memory cards into a new folder, then create a new catalogue for the files in that folder which takes about 10 seconds by the time LR starts. It means that the catalogue (and all the edits on photos) are stored alongside the raw files. It means I never need to apply keywords, build collections etc which all take time and I would never remember the specific keywords to search for anyway ;-)

This makes backing up simple, as well as copying the entire folder to a different machine to work on if required without needing to copy anything else. If I am away for a weekend, I will often copy the Saturday files onto a laptop, perform some initial culling and rating, as well editing a few shots ready for export and publishing when I get home as it saves a few hours work. Just copy the entire directory onto a fast USB3 pen drive from the laptop to main PC when I get home, which can be done at the same time as copying and importing the Sunday RAW files... Obviously, I need to have the same directory structure on both machines to avoid LR not being able to find the files on my desktop when the catalogue is copied across.

If I need to work on some files from a few years ago, I simply copy the directory from one of my backup/archive drives and open the LR catalogue in the directory. If I make any changes, then simply copy the directory back to the archive drive when I'm finished, but won't delete it from my desktop until I backup to another external drive as part of a weekly backup routine.

When editing photos, I often have many shots where the lighting conditions are very similar, so once I've edited one shot to my liking, I'll copy the develop settings and paste them to the others taken at the same time. Ok it's not perfect but gives a good starting point and saves a lot of time with most photos just needing a crop applied. Edits that require a lot of processing and slow down the workflow are dust spot cloning and noise reduction/sharpening so I don't copy these until I'm ready to export the entire batch. I then just do the first one, right click and copy develop settings, tick the boxes for just noise and sharpening, and then select all the edited images and paste. As you are doing wedding shots, you will probably want to tweak each shot individually for printing etc. But if you need to get the majority of files uploaded quickly to a web album for relatives to browse at low resolution, then the above technique will save lots of time once you get the hang of it.

For most of my work, few of the edits I do can actually make use of the GPU, so I have that option switched off to make the overall workflow faster. Admittedly scrolling around a 100% view on an image is slicker with it switched on, but with often tight publishing deadlines - typically before lunchtime the following day for many press outlets or the same day for some, then every second extra soon mounts up.

If someone then wants a print, or hi-res download of a particular image, I'll then spend a few minutes tweaking it further, and maybe opening in Photoshop for some cloning or more detailed dodging and burning if required.

When I first upgraded to LR 6.6, I too found it a nightmare with slowing down every 10 mins or so, but found that quitting LR and restarting cleared the problem so suspected a memory leak problem. I then found that minimising LR and leaving it for 20 seconds also helped a lot - maybe check emails in the meantime. However 6.6.1 has made a noticeable improvement for me, but I still minimise every 10 minutes or so just to be on the safe side, as you don't tend to notice the incremental delay creeping up on you until it gets very bad, by which time you have probably cost yourself a few minutes in wait time for LR to respond.
 
Last edited:
Hi John,

Thanks for the awesome write up ! Tons of info there, I am tempted to send Adobe this thread link - not that they care, but it really comes down to extremely sloppy programming, all those steps you have to take simply to edit and then still stop every 10 mins is very concerning for a pro tool, I am tempted to look at other options if I am to start another catalogue anyway.

I have a little experience with capture one pro 9, so may look into that.

Mean while I will form a decent action plan from your write up - many thanks again John, its hugely appreciated.
 
No worries, hope it helps. I've used LR since version 1 and have evolved my workflow through all the versions to try and get to the same end result as quickly as possible.

I was looking forward to improved performance with V6 which could use the GPU, but moving between images was much slower, even with a 980 graphics card, so ended up switching it off. I'm sure they'll make better use of the GPU when the next version is released at some point in the future.
 
Back
Top Bottom