Lightroom appears to hang on quit

  • 1
  • Question
  • Updated 7 years ago
Quite often after making a number of changes, Lightroom hangs when I try to quit. It appears that if I wait long enough, it will quit (in this case, about 5 minutes after hitting cmd-Q). There is no dialog, no progress bar, just the "spinning rainbow pizza of death". Activity Monitor pegs at 100%, and there is basically no disk activity, so it isn't optimizing the database, and I don't think it is updating metadata on disk.

Any idea what it is doing? Whether force-quitting is a good idea? How I can avoid this?

This time it quit after 5 minutes, but other times I have force-quit. I saved a sample of the process activity, but don't see how to upload it to this site.

Obviously, I am on Macintosh.

A
Photo of Alan Harper

Alan Harper

  • 424 Posts
  • 84 Reply Likes

Posted 7 years ago

  • 1
Photo of jdv

jdv, Champion

  • 728 Posts
  • 56 Reply Likes
Since you are on a Mac, when it does this, open Activity Monitor and "sample" the Lightroom process a few times. Save the results to a file, and offer them to Adobe.
Photo of Alan Harper

Alan Harper

  • 424 Posts
  • 84 Reply Likes
As I said, I have already done this. Should I make my offering elsewhere?
Photo of Dan Tull

Dan Tull, Employee

  • 172 Posts
  • 38 Reply Likes
You can e-mail it to me. Maybe I can pick some clues out of it. My adobe.com e-mail address is dtull. One other thing to look for at quit is whether your memory usage starts high and slowly goes down while the processor is pegged. Most of the things I can think of which would cause quit to take a long time would involve disk I/O, but maybe you've got lots of small data built up and the Lua GC is chewing on it while it works on closing down.

Anyway, feel free to send it along and I'll take a look. Hopefully something will jump out at me. Thanks!
Photo of Alan Harper

Alan Harper

  • 424 Posts
  • 84 Reply Likes
thanks. I will. There was nearly no disk activity (a few kB of data every few seconds), so perhaps it was just freeing memory. I had made lots of metadata changes in an external editor, and then had read metadata for every image. I've had this happen before, I think under similar circumstances.
Photo of jdv

jdv, Champion

  • 728 Posts
  • 56 Reply Likes
Sorry, my mistake. I didn't read to the end where you mention the sample output.