Lightroom 5.5 Crash (GDI Objects Leak)

  • 2
  • Problem
  • Updated 4 years ago
There's a GDI objects leak in Lightroom 5.5 (@Windows 8.1 Pro 64bit). somewhere around 8000 objects Lightroom UI starts to repaint itself very slowly (like a slideshow). At 10K objects it crashes. Usually happens after 1.5h of work.
8K objects screenshot attached
Photo of Ievgen Morskyi

Ievgen Morskyi

  • 4 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 2
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2611 Posts
  • 333 Reply Likes
I can confirm that various panels and menus on my LR 5.5 64-bit running on Windows 7 64-bit seem to leak GDI Objects.

More specifically:

Ctrl-Shift-E-Opening and Esc-Canceling the Export panel uses up 40-60 GDI Objects for each open and cancel, though the number isn't consistent.

Expanding and contracting the Help menu in Library by repeatedly clicking on Help, will consistently consume exactly 12 GDI Objects each time the menu is opened.

Expanding and contracting the Help menu in Develop by repeatedly clicking on Help, will consistently consume exactly 10 GDI Objects each time the menu is opened.

Clicking into the Print module and then to one of the others and back to the Print module seems to consume a few dozen GDI Objects each time Print is clicked on; however, while clicking on a module the first time may consume GDI Objects, clicking amongst modules without clicking on Print doesn't appreciably add more GDI Objects for each click into the module after the first, so Print seems to be a special, wasteful case.

On the other hand, Exporting files don't add to the number for each file only for the panel being brought up, and clicking between folders and on various image thumbnails doesn't necessarily use up handles when clicking back and forth between the same two or three folders or images.

And if I go to another MS program like Outlook or IE and open and close the menus repeatedly GDI Objects don't get used up for each open and close, only the first time a menu is opened.

So it seems to me that LR menus and panels aren't being handled properly.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2611 Posts
  • 333 Reply Likes
Further testing older LR versions on my Win 7 64-bit, shows that LR 5.5 added Menu leaks, LR 5.x added Print leaks, and Export has been leaking for some years, already:

LR 5.5 32-bit leaks the same as LR 5.5 64.bit.

LR 5.4 32-bit: Export panel leaks and Print leaks, but Menus don't.

LR 4.4 64-bit: Export panel leaks, but Print doesn't and the Menus don't.

LR 3.6 64-bit: Export panel leaks, Print unsure, but Menus don't.
Photo of Ievgen Morskyi

Ievgen Morskyi

  • 4 Posts
  • 0 Reply Likes
Knowing adobe's release cycle, we won't see these leaks fixed anytime soon ((.
(should be smth like 5.5.1(2) and not the long hoping and waiting it would be fixed in 5.6, months from now). 'Good' thing 8-10K object count isn't reached within 5-15 min of work(at least in my use case), that would be a major pain'in'the'.

P.S. found the same stuff here:
https://forums.adobe.com/thread/14998...
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2611 Posts
  • 333 Reply Likes
There have been two releases, now, without a release-candidate, and it shows.

What are you doing that is causing the leaks? Surely menus, Export and Print aren't being used so often that they are responsible for using up 10,000 in an hour and a half. I found the three areas by trial-and-error but was not actually processing images.

It would probably be worth your helping Adobe determine what other areas besides the three I found that are leaking.
Photo of Ievgen Morskyi

Ievgen Morskyi

  • 4 Posts
  • 0 Reply Likes
Well, i was going through my travel catalog, around 6k+ of RAWs.
Modules being used - only library and develop. Menu usage was minimal
1) Library module activities (70% of that time, it was closer to 2h actually):
Lens Filtering (LR doesn't want to autorecognize my non-Canon lenses (Zeiss and Tokina; As soon as I select manufacturer manually - it works, but not on AUTO)) Flagging, rating, stacking, keywording, folder rearranging, deleting.
2) Develop module: almost all of available develop tools (except curves), settings syncing, rating, picking, deleting.

That's the gist of it.
Didn't notice any performance issues until that slow repaint occured. Then, being a developer myself, though in a bit different field, I remembered watching Mark Russinovich (expert dev. from MS) talk on GDI objects and decided to check. That's when i saw that 8k number.

P.S. There were also around of 10-15 export operations.
According to helping adobe to find those leaks, it's pretty straightforward, and I'm sure they know how to do it. Guess it's just that it wasn't a serious issue for them until now (and they still may consider this being not-an-issue - e.g. "just restart Lightroom after a while and deal with it...))))").
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2611 Posts
  • 333 Reply Likes
If you haven't already, you can set up default lens assignments using Setup: Save New Lens Profile Defaults after selecting the right lens, then set your LR defaults for lens-profile Setup to use Default instead of Auto and it should work without your having to manually assign them all the time:

Photo of Ievgen Morskyi

Ievgen Morskyi

  • 4 Posts
  • 0 Reply Likes
Thanks a lot for this tip, works like a charm. Got so used to filtering/assigning/syncing that didn't even bother to look for the solution (shame on my lazy *ss)))