Skip to main content
Inspiring
January 17, 2017

P: Memory Leak

  • January 17, 2017
  • 26 replies
  • 868 views

I just left LR idle for a few hours and came back to find my 32GB machine 100% memory with 100% disk due to paging with Lightroom being the culprit.

If I open up System Info from the Preferences->Performance->Camera RAW section, I can watch the "Real memory used by Lightroom" increasing continuously while LR is idle.

Background:

Just upgraded to standalone 6.8. Was previously using LR4 with no problems, but needed new camera RAW support.

I built this machine myself and it has been rock solid and a great performer for 2 years. I use it for software development running linux in a virtual machine to do heavy multi-core compilation and to run compute intensive multi-threaded/multi-core applications for IC design. Never a problem.

OS: Win7 Pro

CPU: Quad core i5-3570

MB: Asus p8z77-v pro

Disk: 8TB configured as a 3T RAID5 array, 4T standalone and 256G SSD

Memory: 16GB just upgraded to 32GB.

This topic has been closed for replies.

26 replies

Inspiring
January 21, 2017
Sounds like Gary's issue is sync related running on CC license and burns through memory slower than my issue.

I'm running perpetual license, no sync and seems to consume memory at a higher rate. 

I haven't had much of a chance to look into it more as I've got a bunch of other irons in the fire, but this issue is definitely impacting my work flow. I often work on large photo sets that take a few hours to go through and sometimes have to restart lightroom to free up memory. That's not a big deal, but if I pop in a large CF with lots of RAW files, or once I've finished post, do a large export and walk away... I come back to a machine brought to it's knees by lightroom.

-b
Participating Frequently
January 21, 2017
😞
Rebooted PC, restarted LR CC with all 3 background tasks paused, minimised it and walked away ... in nearly 10 hrs, it has consumed 3 billion (EU not US billions 😉 cpu cycles, taken 12 1/2 minutes of CPU time, and has a working set of nearly 6 GB and a virtual size of 12.35 GB
And the usage goes up in small increments every 2m exactly
Participating Frequently
January 20, 2017
Ok, paused sync this morning at 31.5GB committed, looks like that may have controlled it, it has actually dropped to 28.5 GB committed now.
I'm going to un-pause and see if it goes up again 😉
Adobe Employee
January 19, 2017
Since you are running the CC version of Lightroom, are you doing any kind of Lightroom mobile syncing when Lightroom is idle? If so, can you pause the Lightroom mobile syncing and see if the memory accumulation still occurs? Thanks.
Participating Frequently
January 19, 2017
Latest CC version of Lightroom, Windows 10, 16GB Ram, it's been running for 23Hrs, I started it and then minimised it, so I have never requested anything from it.
However, it is now using a working set of 4.4GB and over 15GB of Private bytes, and it is steadily taking more and more every 2 minutes. Wonder when/where it'll stop !
Participating Frequently
January 19, 2017
its the CC version, after running overnight its only up to 6.4GB  private bytes and 3.9 GB working set, will leave this system untouched through today and see what it's like tonight.
Adobe Employee
January 18, 2017
Are you running the perpetual license version of Lr 6.8 as well? 
Participating Frequently
January 18, 2017
Most interestingly, the small upwards jumps in Lightroom's Private Bytes usage occur exactly every 120 seconds!
Participating Frequently
January 18, 2017
443 is being used for https support from a virtual machine on my pc.   I disabled the ethernet port but - on restarting LR - it is slowly nibbling away at memory again. I'll leave it running overnight and see what it does!

When ethernet reconnected, I see it talks to
ec2-35-160-189-193.us-west-2.compute.amazonaws.com:https

Memory usage has gone up 0.5 GB over the last 25 seconds of CPU time for Lightroom
Adobe Employee
January 18, 2017
Is your firewall blocking port 443? What happens if you turn off the network connection of the machine altogether?