Bug #11330

Removing pictures from collection doesn't free up RAM

Added by Joe Giampaoli over 3 years ago. Updated over 3 years ago.

Closed: invalid
Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
hardware architecture:


Don't know if it's really a bug but when testing bug 11329 on my laptop with (X)ubuntu 16.04, which has less RAM than my desktop PC, I decided to remove the other images from the collection and just leave on single image to free up RAM which it didn't, so I had to close and relaunch DT so that it would only load that one single image to memory.

Did another test to double check. I even removed all images in collection and RAM was still taking about 50% with DT open. If I launch DT without any files preloaded from my DB it only takes about 12%

Maybe this is more like a feature request? Because maybe I'm not sure how DT handles the memory exactly :)


Screenshot_2016-11-23_12-23-05.png (114 KB) Screenshot_2016-11-23_12-23-05.png Joe Giampaoli, 11/23/2016 08:27 PM


#1 Updated by Tobias Ellinghaus over 3 years ago

That must be something else, the number of images in the collection should have minimal impact in memory usage. Maybe try lowering the thumbnail cache size in prefs ("core" tab, first line).

#2 Updated by Roman Lebedev over 3 years ago

Did you open any images in darkroom? Possibly that memory usage was darkroom caches.

#3 Updated by Joe Giampaoli over 3 years ago

Actually no, I didn't open images at all. I just fired up DT on my laptop without any pictures loaded. Just loaded 8 into the library and memory when up super high and when removing all of the images memory was still used.

The 8 images are super high resolution JPEG's from a Sony. They are about 42 MP size.

My laptop has 4 GB RAM, DT thumbnail cache is set to default 256 MB cache

With htop I measured RAM used by DT:

Nothing loaded: 3.1%
Loaded the 8 High Res shots: 37.1%
Removed all the images from library: remains at 37.1%

Never opened an image in darkroom to edit, but memory remained used, so thumbnail cache isn't removed from memory when removing them from collection, opening a photo to edit with that amount of memory or more already used will make it painful for sure.


#4 Updated by Joe Giampaoli over 3 years ago

Forgot to ask. What would be a good thumbnail cache size for a laptop with these specs?

#5 Updated by Joe Giampaoli over 3 years ago

I just tested with 128 in the thumbnail cache size. I did restart DT after those changes, same test gave me same results, 37.1%

#6 Updated by Tobias Ellinghaus over 3 years ago

Do you have JPEG thumbnails enabled? If not do so (gui tab in prefs, 2nd setting) and try again. Maybe those are the buffers from the background pipe used to generate thumbnails.

#7 Updated by Joe Giampaoli over 3 years ago

Correct! Actually they loaded much faster and memory is at 3.4% with the same set of images. But then my RAW thumbs look crappy. Ah! Decisions! Still I think I like it better with that option disabled. Super fast! So I'll leave it that way from now on because I do work with some really huge files from Real Estate clients and they have really crazy huge res cameras...

OK, thanks Tobias! That was it!

So this bug report can be marked as fixed or null?

#8 Updated by Tobias Ellinghaus over 3 years ago

  • Status changed from New to Closed: invalid

#9 Updated by Roman Lebedev over 3 years ago

  • Target version changed from Future to 2.2.0

Also available in: Atom PDF

Go to top