Project

General

Profile

Bug #9965

lighttable stuck in regenerating preview

Added by Stefan Agner over 5 years ago. Updated over 5 years ago.

Status:
Closed: invalid
Priority:
Critical
Assignee:
-
Category:
Lighttable
Target version:
-
Start date:
05/20/2014
Due date:
% Done:

0%

Estimated time:
Affected Version:
1.4.2
System:
other GNU/Linux
bitness:
64-bit
hardware architecture:
amd64/x86

Description

When in lighttable mode darktable is stuck regenerating thumbnail images. Often this is even visible by dis- and reappearing preview images. On my quad core system, two cores are running at 100%. My library contains about 500 images (JPEG and NEF). Deleting the library database and regenerating it didn't solved the issue.

GDB backtrace (all other threads are in libc, :

Thread 9 (Thread 0x7fffe9ea8700 (LWP 7489)):
#0  0x00007ffff79dbf14 in dt_imageio_jpeg_decompress () from /usr/bin/../lib/darktable/libdarktable.so
No symbol table info available.
#1  0x00007ffff79d9d02 in dt_imageio_large_thumbnail () from /usr/bin/../lib/darktable/libdarktable.so
No symbol table info available.
#2  0x00007ffff79e6d1f in ?? () from /usr/bin/../lib/darktable/libdarktable.so
No symbol table info available.
#3  0x00007ffff79e9a30 in dt_mipmap_cache_read_get () from /usr/bin/../lib/darktable/libdarktable.so
No symbol table info available.
---Type <return> to continue, or q <return> to quit---
#4  0x00007ffff7a09a6b in dt_image_load_job_run () from /usr/bin/../lib/darktable/libdarktable.so
No symbol table info available.
#5  0x00007ffff7a020bf in dt_control_run_job () from /usr/bin/../lib/darktable/libdarktable.so
No symbol table info available.
#6  0x00007ffff7a02228 in dt_control_work () from /usr/bin/../lib/darktable/libdarktable.so
No symbol table info available.
#7  0x00007ffff7726124 in start_thread () from /usr/lib/libpthread.so.0
No symbol table info available.
#8  0x00007ffff745a4bd in clone () from /usr/lib/libc.so.6
No symbol table info available.

Thread 8 (Thread 0x7fffea6a9700 (LWP 7488)):
#0  0x00007ffff79dbf38 in dt_imageio_jpeg_decompress () from /usr/bin/../lib/darktable/libdarktable.so
No symbol table info available.
#1  0x00007ffff79d9d02 in dt_imageio_large_thumbnail () from /usr/bin/../lib/darktable/libdarktable.so
No symbol table info available.
#2  0x00007ffff79e6d1f in ?? () from /usr/bin/../lib/darktable/libdarktable.so
No symbol table info available.
#3  0x00007ffff79e9a30 in dt_mipmap_cache_read_get () from /usr/bin/../lib/darktable/libdarktable.so
No symbol table info available.
#4  0x00007ffff7a09a6b in dt_image_load_job_run () from /usr/bin/../lib/darktable/libdarktable.so
No symbol table info available.
#5  0x00007ffff7a020bf in dt_control_run_job () from /usr/bin/../lib/darktable/libdarktable.so
No symbol table info available.
#6  0x00007ffff7a02228 in dt_control_work () from /usr/bin/../lib/darktable/libdarktable.so
No symbol table info available.
#7  0x00007ffff7726124 in start_thread () from /usr/lib/libpthread.so.0
No symbol table info available.
#8  0x00007ffff745a4bd in clone () from /usr/lib/libc.so.6
No symbol table info available.

I'm using darktable from ArchLinux repository, 1.4.2-3.


Related issues

Related to darktable - Bug #9891: Darktable becomes non-responsive when maximized to full screenNew04/04/2014

Related to darktable - Bug #9966: Thumbnails on lighttable are blinkingClosed: invalid05/20/2014

History

#1 Updated by Stefan Agner over 5 years ago

I forgot to mention, removing or deleting photos doesn't work anymore. I get the confirmation dialog, but after confirming the deletion, the photo doens't disappear.

#2 Updated by Stefan Agner over 5 years ago

The problem actually sounds similar to #9891. I'm using an Intel graphic card (Haswell generation).

#3 Updated by Roman Lebedev over 5 years ago

  • Related to Bug #9891: Darktable becomes non-responsive when maximized to full screen added

#4 Updated by Roman Lebedev over 5 years ago

  • Assignee deleted (Stefan Agner)

#5 Updated by Roman Lebedev over 5 years ago

  • Related to Bug #9966: Thumbnails on lighttable are blinking added

#6 Updated by Ulrich Pegelow over 5 years ago

Please have a look at #9966 and see if a similar solution works for you.

#7 Updated by Stefan Agner over 5 years ago

This solved it for me too. Beside setting the default to something useful the user should get a warning that mipmap cache is too small rather than being stuck in a loop.

#8 Updated by Ulrich Pegelow over 5 years ago

  • Status changed from New to Closed: invalid

Well, if the cache is so small the user has probably set it to that low value. One solution could be defining a minimum value of a few hundred MB. However, that may take away options to get darktable running on 32-bit systems. I consider to add an FAQ section to the manual which would cover this not so infrequent topic.

Also available in: Atom PDF

Go to top