12 Messages
•
320 Points
Mon, Dec 31, 2018 12:54 PM
Lightroom Classic: Serious memory leak
For a long time I am troubled by a huge memory consumption of my system. Today I digged more deeply into what is going on with all the memory being used by no processes. Windows 10 Task Manager was showing more than 21GB of RAM used. However, there were only three memory hungry processes listed in the Processes tab: Adobe Lightroom Classic CC eating up 3.5GB, Firefox 2.5GB and Adobe Bridge with roughly 1GB. All the processes listed could add up to no more than 8GB of memory.
In my next step I tried to follow this article: https://aloiskraus.wordpress.com/2017/02/26/the-mysterious-lost-memory-which-belongs-to-no-process/
RAMMap was showing 17.7GB in Active Process Private memory. It was clear from the Processes tab that all the remaining memory was allocated by the "MemCompression" process. I then decided to exit Lightroom Classic CC to see what hapens. Whooping 12GBs were released instead of the 3.5GB shown in Task Manager. When starting Lightroom again, 3.5GB is shown in Task Manager as before and the same amount shows in RAMMap under Lightroom's private memory.
I am using Lightroom Classic CC on my developer notebook with 32GB of RAM and do not currently have another machine with less physical memory available to test the behavior. In the time of discovering the issue I was working in the Development module with a set of 2 500 photos filtered to a view of only 224 images.
In my next step I tried to follow this article: https://aloiskraus.wordpress.com/2017/02/26/the-mysterious-lost-memory-which-belongs-to-no-process/
RAMMap was showing 17.7GB in Active Process Private memory. It was clear from the Processes tab that all the remaining memory was allocated by the "MemCompression" process. I then decided to exit Lightroom Classic CC to see what hapens. Whooping 12GBs were released instead of the 3.5GB shown in Task Manager. When starting Lightroom again, 3.5GB is shown in Task Manager as before and the same amount shows in RAMMap under Lightroom's private memory.
I am using Lightroom Classic CC on my developer notebook with 32GB of RAM and do not currently have another machine with less physical memory available to test the behavior. In the time of discovering the issue I was working in the Development module with a set of 2 500 photos filtered to a view of only 224 images.
Problems
•
Updated
8 months ago
376
9
Helpful Widget
How can we improve?
Tags
No tags available
Responses
jeffgo
104 Messages
•
1.6K Points
2 years ago
0
0
katrin_serova
29 Messages
•
522 Points
2 years ago
0
tristan_schmurr_hay42semy11vn
2 Messages
•
134 Points
2 years ago
0
Rikk
Adobe Administrator
•
9.5K Messages
•
130.8K Points
2 years ago
Open the TestHighMemoryUsageCopy.LRCAT file in Lightroom and attempt the same operation(s) that caused the high memory usage.
Does the high-memory usage repeat with the test catalog?
Quality Engineering - Customer Advocacy
4
ruby_k_eze1w2xvinds8
Employee
•
27 Messages
•
664 Points
2 years ago
2
mark_jones_kl34zeu6flz1p
1 Message
•
120 Points
a year ago
1
jose_quiroz
1 Message
•
64 Points
a year ago
Things I tried:
Tried other catalogs, they were good, culprit was this one.
Deleting the newly upgraded catalog as to force Lr to re-create one for the old one.
Deleting the previews and temporary files left behind after force quitting.
Opening Lr and closing it quickly before the RAM usage went over 5GB so it would come to terms with its temporary files
Restarting
Deleting the slideshow
No luck.
I got suspicious about the soundtrack. I removed the tracks I was using and that were kept as part of the default template in the Slideshow module, closed Lr quickly before RAM usage went crazy.
Opened it again, RAM was happily around 600MB, added the original track, and after 10 minutes of playing with it and let it idle, RAM still sits at ~630 MB.
Hardly your case guys, but hopefully that will give Adobe some free troubleshooting facts to help fixing the issue.
I hope that sheds some light.
2
0
martijn_saly_5922019
223 Messages
•
3.5K Points
a year ago
I'm DM'ing with Adobe on Twitter, and every single bloody time they promise me to "loop in an expert" and that they're "investigating the problem" and that they're so sorry that I'm having this experience.
I find it difficult to believe they're being genuine.
So the question is, how on great mother Earth can we put some pressure on Adobe to fix this problem?!
1
ryan_smith_5683064
41 Messages
•
676 Points
8 months ago
3
0