Bug #9727

Lighttable view constantly refreshes pictures over and over again

Added by Olaf Gottschalk over 6 years ago. Updated over 6 years ago.

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


Estimated time:
Affected Version:
hardware architecture:


After today's update to 1.4rc1+110~gcc368d6, in lighttable view mode, I see all visible pictures constantly being refreshed over and over again - without any interaction.
This is extremely annoying especially when viewing only a handful of pictures.
Don't know why this is done and how I could stop it.

On my system all my RAWs are on an nfs mount to a Synology NAS, but that may not have to do anything with that behavior.

settings.png (49.1 KB) settings.png Olaf Gottschalk, 12/19/2013 08:26 PM


#1 Updated by Olaf Gottschalk over 6 years ago

It also adds a constant CPU load which is very bad... :-(

#2 Updated by Ulrich Pegelow over 6 years ago

Please have a look into the preferences dialog, namely core options. Look for the first setting (memory in megabytes for mipmaps cache). What size is defined there?

#3 Updated by Olaf Gottschalk over 6 years ago

512 MB - I never changed that value, though and never saw this happening. Should the value be increased?

By the way: I just notice that the German names of the options are a little... wacky..., too. :-) It says "Speicher in Megabytes, der für den MIP-MAP-Cache benutzt wird" but "Speicherlimit (in MB) für Kachelung" and "Minimale Speichermenge (in MB)". Shouldn't it be either "(in MB)" for all OR " in Megabytes" for all?
Or better to put the unit behind the text in square brackets for all options alike? ;-)

#4 Updated by Olaf Gottschalk over 6 years ago

Okay, I just increased that cache value to 1024 MB. Now it's fine - CPU load is down to 0 again, no pictures get refreshed while doing nothing on the lighttable view. Luckily I got 10GB RAM...

I still think this is a bug because it doesn't make any sense to constantly update the previews in the lighttable - if the memory is too low to hold 6 pictures (in 512MB?) - what is going on in that cache? And why did this behavior start just in the recent update?

#5 Updated by Ulrich Pegelow over 6 years ago

  • % Done changed from 0 to 100
  • Status changed from New to Fixed

It's not clear what caused the problem. Might be that the mipmap cache (the cache holding all thumbnails) got corrupted and changing the cache size fixed it. In case of further problems please first try if removing the cache file ($HOME/.cache/darktable/mipmap*) solves the issue. If the problem persists please reopen the ticket.

Also available in: Atom PDF

Go to top