LocalHero1953 Posted July 12, 2016 Share #1 Posted July 12, 2016 Advertisement (gone after registration) I've been finding a problem with LR since the latest upgrade: it runs slower and slower during a session. I missed it at first as the upgrade coincided with me doing more work in Photoshop with layers, then reverting to LR - I thought my files were getting too big. I upgraded my RAM from 12 to 24 Gb, but found no improvement. (I'm running Windows 10) A bit of googling (look for "Lightroom memory leak" reports from the last few months) shows this is a problem other people have had, but I haven't seen a solution. The problem can be seen if you run the System Monitor for RAM usage - you can see RAM use increasing continuously as you work in LR, even if the file is relatively small and is simply a DNG with some relatively minor edits. Switching between modules slows to a crawl and applying local adjustments take an age to be implemented. Sometimes the screen goes black while it works on the file. One temporary trick is to minimise LR briefly (1-2 secs) then maximise it - the RAM use drops to the original level again. On Adobe forums it is described as a memory leak problem, and various Adobe reps have seen it but not come up with a solution (other than reverting to a previous version). Anyone else have this problem here? Anyone seen it on a Mac? Quote Link to post Share on other sites More sharing options...
Advertisement Posted July 12, 2016 Posted July 12, 2016 Hi LocalHero1953, Take a look here Lightroom CC 2015.6 memory problem - running slow. I'm sure you'll find what you were looking for!
hoppyman Posted July 13, 2016 Share #2 Posted July 13, 2016 you could try clearing your cache and restarting LR. That worked for me after long editing sessions Quote Link to post Share on other sites More sharing options...
LocalHero1953 Posted July 13, 2016 Author Share #3 Posted July 13, 2016 I tried that early on - no, it didn't work. This does seem to be a real problem of memory management, not related to cache, GPU, file size etc. Plenty of others have reported the same issue with the current version, without any change in work flow that could have caused it. OTOH, clearly not everyone encounters it, else I suspect it would be more widely known. Quote Link to post Share on other sites More sharing options...
Guest satrycon Posted July 13, 2016 Share #4 Posted July 13, 2016 i use version 6.6 on macbook pro, 16gb RAM...the internal 1TB SSD helps..lightroom likes a good GPU card..no slowdowns on my mac..and my 5DSR raw files are an average of 55MB.. the only time ive seen a slowdown was last week when i had a 23 image stich in lightroom..after processing i removed that file from the catalog and re-saved..then no slowdown Quote Link to post Share on other sites More sharing options...
Exodies Posted July 13, 2016 Share #5 Posted July 13, 2016 The last update of Lightroom CC on my Mac has a problem. Twice when switching to LR after a sleep the program has not responded; force quit was necessary. I don't think it was memory because other apps were working smoothly but I'll check that next time. Quote Link to post Share on other sites More sharing options...
LocalHero1953 Posted July 13, 2016 Author Share #6 Posted July 13, 2016 (edited) I should have added, that I have 2x1Tb SSD drives, one of which is dedicated to the LR catalogue and a 200GB Adobe cache, so I wouldn't expect any delays there. As with others reporting this issue, it has only happened with the latest update, which appears to rule out problems with workflow or local PC settings/hardware. Edited July 13, 2016 by LocalHero1953 Quote Link to post Share on other sites More sharing options...
willeica Posted July 13, 2016 Share #7 Posted July 13, 2016 (edited) Advertisement (gone after registration) I have been having problems for the last week or so with Lightroom CC 2015.6. I am using an iMac (4 weeks old) with the latest version of El-Capitan. Last week I had to contact the Adobe Help Desk and they got me up and running again ; for just a few days! For the last few weeks the dreaded Apple Photos download box has been appearing and I managed to get rid of it by clicking cancel. Then it got nasty after my call to the Adobe Help Desk and I had to click 'not for this device' to get rid of it. Yesterday I found, however, that when I give the import command in Lightroom I just get spinning coloured wheels and cannot access any import device in Lightroom. I tried using Auto Import and it worked but it will just pile all of the photos into a single folder, albeit in date sequence. This means, however, that I have to get the photos into a folder for auto-import. Yesterday I did it by copy and paste but, I imagine that I can use Photos to get the photos into the auto import folder for Lightroom. I hope that the above makes sense. What this means, in effect, is that what once was a one stage process is now a multi-stage process. Hardly progress. I do not know whether to blame Adobe or Apple as I trust neither company. I believe that all of this is about selling cloud space 'real estate' which I do not want or use and my system is punishing me for this. Before someone asks why I use Lightroom CC, I got a Fuji X-Pro 2 which requires LR CC to process its RAW output. In summary, both Apple and Adobe provide a considerably worse level of service than a few years ago. Importing into Lightroom with Mountain Lion and earlier versions of Lightroom was a dream by comparison to what I am getting today. It really is a case of one step forwards and about 3 steps backwards. Any suggestions as to how I can get around these issues would be welcome. William Edited July 13, 2016 by willeica Quote Link to post Share on other sites More sharing options...
jaapv Posted July 13, 2016 Share #8 Posted July 13, 2016 Hmm.. I probably could balance this with threads full of developing/darkroom woes... Quote Link to post Share on other sites More sharing options...
jaapv Posted July 13, 2016 Share #9 Posted July 13, 2016 I have been having problems for the last week or so with Lightroom CC 2015.6. I am using an iMac (4 weeks old) with the latest version of El-Capitan. Last week I had to contact the Adobe Help Desk and they got me up and running again ; for just a few days! For the last few weeks the dreaded Apple Photos download box has been appearing and I managed to get rid of it by clicking cancel. Then it got nasty after my call to the Adobe Help Desk and I had to click 'not for this device' to get rid of it. Yesterday I found, however, that when I give the import command in Lightroom I just get spinning coloured wheels and cannot access any import device in Lightroom. I tried using Auto Import and it worked but it will just pile all of the photos into a single folder, albeit in date sequence. This means, however, that I have to get the photos into a folder for auto-import. Yesterday I did it by copy and paste but, I imagine that I can use Photos to get the photos into the auto import folder for Lightroom. I hope that the above makes sense. What this means, in effect, is that what once was a one stage process is now a multi-stage process. Hardly progress. I do not know whether to blame Adobe or Apple as I trust neither company. I believe that all of this is about selling cloud space 'real estate' which I do not want or use and my system is punishing me for this. Before someone asks why I use Lightroom CC, I got a Fuji X-Pro 2 which requires LR CC to process its RAW output. In summary, both Apple and Adobe provide a considerably worse level of service than a few years ago. Importing into Lightroom with Mountain Lion and earlier versions of Lightroom was a dream by comparison to what I am getting today. It really is a case of one step forwards and about 3 steps backwards. Any suggestions as to how I can get around these issues would be welcome. William I am glad I am always one OS behind... Couldn't you reinstall your Mac with Mountain Lion? If needed as a dual-boot system? Quote Link to post Share on other sites More sharing options...
willeica Posted July 13, 2016 Share #10 Posted July 13, 2016 I am glad I am always one OS behind... Couldn't you reinstall your Mac with Mountain Lion? If needed as a dual-boot system? Thanks Jaap. I'm not sure that a Mountain Lion re-install would work. Its funny that you should say that, though, as the guy in the Apple dealer where I bought the my new iMac actually said that unless El-Capitan was already pre-loaded, I should not upgrade. Unfortunately it was pre-loaded. Life is too short for 'dual-boot', whatever that might entail. The decline in the quality of Apple and Adobe products goes back to the introduction of cloud services by both a few years ago. I have seen a lot of 'remember the Alamo' posts on this forum from 'hold outs' who are keeping stand alone Lightroom, but the software majors rumble on providing the service that they want you to have rather than the service that you want. A friend of mine who is an Apple enthusiast says that Photos is for the ordinary user who does not want fancy things like Lightroom. It sounds like ever decreasing circles to me and that there must eventually be a gap in the market for software for people like ourselves who want to do 'fancy things' with photographs. William Quote Link to post Share on other sites More sharing options...
jaapv Posted July 13, 2016 Share #11 Posted July 13, 2016 Dual Boot means that you have both operating systems available at startup and can choose between the two of them. Find a 15-year old with his baseball cap the wrong way around and he will set it up for you in no time. Quote Link to post Share on other sites More sharing options...
willeica Posted July 13, 2016 Share #12 Posted July 13, 2016 Dual Boot means that you have both operating systems available at startup and can choose between the two of them. Find a 15-year old with his baseball cap the wrong way around and he will set it up for you in no time. Thanks. I have one, he's a bit older and he's my grandson, and he has built his own PC with water-cooling and an SSD. I have had some suggestions from a friend whose son works on Macs and I will follow that before letting the young fellow loose. William 1 Quote Link to post Share on other sites More sharing options...
LocalHero1953 Posted August 7, 2016 Author Share #13 Posted August 7, 2016 There is now an update to Lightroom CC 2015.6, listed as 2015.6.1, which is purely a bug fix update. One of the bugs listed as fixed is "An issue that resulted in high memory usage while in the Develop module", which looks like what I had. I'm still downloading. I only found this update because I was getting such poor performance that I was trying to find out how to roll back to the previous version. http://blogs.adobe.com/lightroomjournal/2016/07/lightroom-cc-2015-6-1-now-available.html Quote Link to post Share on other sites More sharing options...
Jeff S Posted August 8, 2016 Share #14 Posted August 8, 2016 (edited) The decline in the quality of Apple and Adobe products goes back to the introduction of cloud services by both a few years ago. Apple has been focused on mobile, getting slow and sloppy with desktop to the point that its former advantages over Windows are dwindling. And Apple desktop hardware now seems more about design than function. Adobe has intentionally frustrated users of standalone LR, which I think will end soon, leaving the subscription only model. Jeff Edited August 8, 2016 by Jeff S Quote Link to post Share on other sites More sharing options...
LocalHero1953 Posted August 8, 2016 Author Share #15 Posted August 8, 2016 So far, it looks like the update has cured the problem Quote Link to post Share on other sites More sharing options...
hoppyman Posted August 8, 2016 Share #16 Posted August 8, 2016 (edited) I haven't seen an improvement there yet myself. I am still needing to restart after functions in the develop module become very sluggish and I sometimes find the program no longer responsive. Still working on whether I have a mis configuration or this is just a function of how many large files are in my typical import and editing. I go out to Ps for some functions from LR Edited August 8, 2016 by hoppyman Quote Link to post Share on other sites More sharing options...
LocalHero1953 Posted August 8, 2016 Author Share #17 Posted August 8, 2016 I found a few other comments on the bug recently: it seems to be related to the Develop module in particular, and when working through a series of images - perhaps related to poor management of RAM used for screen display data. I haven't done enough yet to confirm an improvement, but it seems OK so far. Quote Link to post Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.