Lightroom CC hangs during export if computer is left unattended

  • 4
  • Problem
  • Updated 3 years ago
  • (Edited)
If I send a series of files to export and leave the computer unattended while it happens I return to find that Lightroom has stopped responding and the export stopped about 5-10 minutes after it started. I have to force quit Lightroom from the Activity Monitor and re-launch it in order to continue.

Lightroom CC
Mac OS X 10.9.5
Energy saver preferences are set to never sleep the computer.
Lightroom mobile preferences are set to prevent sleeping during sync

Exporting works fine as long as I am using the computer to do something (doesn't matter if LR is used or not). while the export takes place. I have been using Lightroom since V1 and have not encountered this problem before. It showed up immediately when I updated to CC.

Any thoughts?
Photo of Bryan Hewitt

Bryan Hewitt

  • 15 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 4
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
Does it happen if you try one of those export sessions with the GPU acceleration off in the preference dialog?

Do you have a crash log?
Photo of Ryo Yanagida

Ryo Yanagida

  • 1 Post
  • 0 Reply Likes
I've come across very similar issue, I've managed to take some spindumps.
It isn't really a crash but becomes unresponsive for a minimum couple minutes and I tend to kill them.
I've come across this issue while handling library related operations like import, export and changing folder.
It also tends to happen while in background, i.e. start exporting and leaving them to do so in the background while I do other things.
Photo of Bryan Hewitt

Bryan Hewitt

  • 15 Posts
  • 0 Reply Likes
Now that I have brought 10K+ photos through from ingest to completion using LR since I originally posted this, I can verify that the entire application runs more smoothly on my system with the GPU acceleration turned OFF.
Photo of Bryan Hewitt

Bryan Hewitt

  • 15 Posts
  • 0 Reply Likes
Thanks for the quick response. I haven't tried turning off GPU acceleration. Will do next time I export. How would I locate/transmit a crash log to you?
Photo of Bryan Hewitt

Bryan Hewitt

  • 15 Posts
  • 0 Reply Likes
I also have the ATI Radeon HD 5770 graphics card. It isn't on the list of unsupported cards here:

https://helpx.adobe.com/lightroom/kb/...

But I thought I would put it out there in case it was helpful.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
You would typically see two dialogs coming up when an Adobe application crashes. One would send the crash to Apple and the second one would send the crash to Adobe. Choose to submit both. The dialog would also provide details on the crash where you can copy and paste as well.
Photo of Bryan Hewitt

Bryan Hewitt

  • 15 Posts
  • 0 Reply Likes
Thanks for the info. I do see that most of the time when Adobe applications crash. This issue does not generate either of the crash reporter dialogs. Lightroom hangs indefinitely and is listed as "not responding" in the Activity Monitor. All other applications work as expected, but LR does not respond in any way to any selections made through the menus from within LR or to keyboard shortcuts. I have to go to the Activity Monitor, select it in the list of running processes and choose Force Quit. It quits immediately. Then I re-launch it and keep working. Is there another way that I could get the info that would be in a crash report and submit it?
Photo of Bryan Hewitt

Bryan Hewitt

  • 15 Posts
  • 0 Reply Likes
Thanks for doing that. Those things are not really my area of expertise.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 716 Reply Likes
OK, on MacOS 10 you can sample the running app to see what it is doing, or where it is hung.

Do you know how to use Activity Monitor (in Applications/Utilities)? Basically just launch the app, select LightRoom, double click on LightRoom, then in the dialog that opens up select the "Sample" button in the lower left corner. It'll take a minute or two to sample and generate the report -- then the LR engineers can use the report to get some idea of where the application got hung up.
Photo of Bryan Hewitt

Bryan Hewitt

  • 15 Posts
  • 0 Reply Likes
I will give that a try. I'm in the middle of working on a job right now that will be completed today, so I can try another export soon. Can I use the Activity Monitor to sample and generate a report any time, or does it need to me sampling while LR hangs?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 716 Reply Likes
You need to sample while it is hung, so we can see where it is hung. Sampling at another time will only tell us what it was doing that that particular time...
Photo of Bryan Hewitt

Bryan Hewitt

  • 15 Posts
  • 0 Reply Likes
OK. I will sample the Lightroom Process in Activity Monitor each time I export. My work for today is finished, but I have more tomorrow. I will report the results back here once I export. Thanks for your help on this.
Photo of Bryan Hewitt

Bryan Hewitt

  • 15 Posts
  • 0 Reply Likes
I did 2 test exports yesterday while sampling with Activity Monitor. Both completed successfully with no errors or hangs. I have also been able to export 3 small completed jobs with no problems yesterday and today.

Previous to the exports, I turned the GPU acceleration off and on to test the performance of several difference tasks that I regularly carry out in LR. I uncovered the following that may be of interest:

With GPU acceleration turned on, the Dust Removal tool was very sluggish, and often erratic in its behavior. This is something that has been going on since LR v5, and I have seen it across multiple machines with different OS X builds both in my studio and at the school where I teach. I wasn't sure how to document and report it because it seemed to be fairly random and I was unable to identify the series of operations that caused it. With GPU acceleration turned off, the same tool used to complete the same actions is smooth and responsive on my system. Since I process up to 5,000 images a week using LR, a few seconds per image that I can save is a big deal. So far I am very happy about the increased performance of the Dust Removal tool. Thanks for the tip about GPU acceleration.

Going back to the original issue of hang during export, I am a little confused. Also very happy that I did not experience it on the most recent exports. This is because I made sure that all conditions were identical to those that produced the hang on previous exports, even the time of day and the drives where files where being sent to and taken from. The only difference between all of the times I have exported from LR CC where it hung and the 5 times when it did not is one of two things.

1. Activity Monitor was running and sampling the process during the entire export operation on the first 2 of the 5 successful exports.

2. GPU acceleration was turned off and on several times during the editing phase before each of the exports. I made sure to turn it back on for the exports to duplicate the conditions that had previously resulted in a hang.

Does any of this make sense and/or does anyone with greater expertise than I do with these matters have any suggestions?

Even though my own system is currently working better, I would be interested to learn more about this because I teach Lightroom to several hundred students every semester, as well as doing consulting work for clients who are building Lightroom-based photo-editing workstations. Any tips on how to speed up the application and increase reliability are always very welcome.
Photo of Mark Harris

Mark Harris

  • 3 Posts
  • 0 Reply Likes
I have similar issues.
Most mornings I find LR hung with exactly 100% CPU usage, even when I left it doing nothing.
I let my iMac sleep, with powernap.
LR CC + OSX 10.10.3
Photo of Bryan Hewitt

Bryan Hewitt

  • 15 Posts
  • 0 Reply Likes
Mark,

I have had that same experience on occasion, where LR hangs and uses 100% CPU. So far haven't been able to diagnose what operations cause it.

I have also been experiencing progressively slower performance in the Library module. Even when I rendered both standard and 100% previews for every photo I was reviewing, the Library module would take more and more time to load a preview the more photos I looked at. The first 50-100 or so would load instantly, but once I got 3-400 photos in, things slowed to the point where I was waiting up to 15 seconds for each preview to load.

Since I deal with up to 7K images a week, that kind of lag time really adds up to me spending up to 30 hours a week waiting for Lightroom to load previews. Since I can't bill more for my software being slow, I went looking for other options.

Since I switched to Photo Mechanic for the sorting/culling phase, the time it takes me to deliver on my shoots has been more than cut in half.

has anyone else had the experience of previews taking longer to load the more images the user looks at during a session? Both my LR catalog and previews are on SSD drives, so I know it isn't an issue with drive speed.
Photo of Mark Harris

Mark Harris

  • 3 Posts
  • 0 Reply Likes
I had the same experience with previews slowing down a long time ago, and that turned out to be due to too-small cache. I now have 100 GB cache on SSD.
Photo of Bryan Hewitt

Bryan Hewitt

  • 15 Posts
  • 0 Reply Likes
Mark,

Thanks for posting that. Good to know I'm not the only one with that issue. When I set up my current system I built it with a special SSD just for caches from ACR, LR and PS. My Lightroom cache is the same size as yours (100GB). It gave me a few more previews to look at before slowing down, but did not solve the issue. Is your cache on the same physical drive as anything else, or is it on a separate drive like mine?

I noticed that, even though the Adobe documentation says it would be faster to put the catalog on a different drive than the Lightroom application, I realized a slight speed increase overall throughout the application by placing the catalog in the Pictures>Lightroom folder. I am wondering if it might actually be faster to use the same SSD for the cache as the application.
Photo of Mark Harris

Mark Harris

  • 3 Posts
  • 0 Reply Likes
I have it on the same SSD, just for convenience. When I made the big cache, I remember too that it helped but didn't cure.
Why I haven't noticed the problem recently is probably that I upgraded from an old Mac Pro to a new iMac when I got a D800, and it just has performance to spare, even when the cache fills.