Skip to main content
Adobe Photoshop Family

8 Messages

 • 

216 Points

Thu, Jul 14, 2016 6:31 PM

Closed

CC Lightroom 2015.6 - *BAD* memory leak during import

Really really bad memory leak on ‘import’. Running OS X El Capitan. Lightroom starts up ok (although it could be quicker) into ‘develop’ module. Selecting ‘import’ I don’t even get the opportunity to choose an import source before I get the ‘spinning beachball’ (Apple’s equivalent of the Microsoft hourglass).

And if I track the process, OS X thinks Lightroom is ‘not responding’ while I can sit and watch the memory usage go up and up. I’ve let it get to about 12.5 GB (yes, gigabytes) before I kill off the Lightroom process – it was still getting bigger quite rapidly. Once Lightroom is killed, the memory use then immediately drops to normal levels.

This is critical. Without the ability to import photos, the software is useless to me.

This conversation has been merged. Please refer the main conversation:

Responses

Employee

 • 

1.7K Messages

 • 

32.4K Points

4 years ago

Hi Jon, I assume you haves lots of RAM on the machine, 32GB? It is not memory leak in that the memory usage would keep growing. For now, I recommend revert back to Lr CC 2015.5.1 by following https://helpx.adobe.com/lightroom/kb/roll-back-to-prior-update.html since you have two issues. The fixes are on its way soon.

You can try https://feedback.photoshop.com/photoshop_family/topics/lightroom-interactive-speed-gpu-usage to try to resolve the memory usage issue.

Principal Scientist, Adobe Lightroom

8 Messages

 • 

216 Points

4 years ago

No. I have as much RAM as Apple will permit me to install - unfortunately, due to the mysteries of Apple's engineers, that's only 4GB of physical memory. I'm intrigued by your assessment: as an IT professional myself, when I merely select a module in the application (i.e. I haven't asked it to actually do any import work yet) and then I can sit and watch the memory usage go up and up - despite me not selecting anything else - without stopping, until I manually kill the process; that's what I'd describe as a memory leak. (The memory demands are being delivered via virtual memory.)

I'll try downgrading when I have an hour free. Thanks for the link.

Not sure why the GPU should be an issue? In terms of general slowness, can you confirm that the CC variant isn't trying to do anything over the internet? I'm increasingly forced down the 'always online' route by various software vendors, but the reality of life in rural UK is that we're lucky to get much more than 1 Mbps in download speed - so (despite opting out of any cloud/online functionality that I can) any bits of software that try to do clever online stuff are not going to work well.  

27 Messages

 • 

420 Points

4 years ago

I'd just like to confirm Jon's issue. I have the same issue. Click import and Lightroom starts to gobble up all ram available. It doesn't happen all the time though. Just 3 out 4 attempts. It depends on the sequence of events (yet to confirm). Typically start LR with card already in reader or phone plugged in. Click import and get ready to force quit! If I start it without the card then then insert the card and click import it will, most of the time, work. However, even then, it will often start on it's trek to memory oblivion!! Latest El Capitan, latest Lightroom, CC etc...

8 Messages

 • 

216 Points

4 years ago

Simon,

You said a couple of weeks back that the fixes are on their way soon, implying that Adobe (a) recognises that a problem exists, (b) has identified the root cause, and (c) is actively working on a fix.

Is there a date when we can expect the fix to be available, please? 

13 Messages

 • 

306 Points

4 years ago

Yes, Simon.  How do you define "soon."  Thinking about jumping ship here.

Employee

 • 

1.7K Messages

 • 

32.4K Points

4 years ago

Very soon :-).

Principal Scientist, Adobe Lightroom

8 Messages

 • 

216 Points

4 years ago

Simon,

I understand that you probably can't commit Adobe to a date, but how about giving us a clue - we're being very patient (considering this has stuffed my workflow - lucky I'm not a pro or it would be much more serious).

Are we talking days...weeks.....months?

Champion

 • 

5.8K Messages

 • 

102.3K Points

Jon, he just gave away as much as he possibly can... hold that thought.

8 Messages

 • 

216 Points

I'm really (really really!) trying to be nice. I'd be a lot happier if we all got an official statement from Adobe, acknowledging the shortcomings in the latest version and promising a fix Real Soon Now.

Given that we've now been coerced into a subscription based deal (not my choice but, since there aren't any practical alternatives, I don't have much choice) I'd expect a rather more proactive official response from Adobe, rather than one of its employees (albeit a helpful one - thanks Simon!) giving us all the hints that he can.