Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#1034509: darktable: Crashes when scrolling through a collection

50 views
Skip to first unread message

Michael Below

unread,
Apr 17, 2023, 8:50:04 AM4/17/23
to
Package: darktable
Version: 4.2.1-4
Severity: normal
X-Debbugs-Cc: be...@judiz.de

Dear Maintainer,

I imported a collection of about 400 Fuji E4 RAW images (.RAF). I was able to go through all images for a first cull. Now I want to edit the remaining images. When I reach about half of the remaining collection darktable crashes while generating previews in the lightroom view. On the command line, I get “Speicherzugriffsfehler darktable” (memory access error).

I tried running darktable with the -d cache argument, then I get a lot of output like “generate mip 3 for image 7279 from scratch”. But there is no indication why it crashes.

I was able to import the directory with the collection in shotwell without crashing, it shows thumbnails for all 400something images. Other collections with a similar number of images do not show the issue.

Any ideas what to try next?

Thanks for your work!

Cheers
Michael

-- System Information:
Debian Release: 12.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'stable'), (50, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages darktable depends on:
ii libavif15 0.11.1-1
ii libc6 2.36-8
ii libcairo2 1.16.0-7
ii libcolord-gtk1 0.3.0-3
ii libcolord2 1.4.6-2.2
ii libcups2 2.4.2-3
ii libcurl3-gnutls 7.88.1-8
ii libexiv2-27 0.27.6-1
ii libgcc-s1 12.2.0-14
ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii libglib2.0-0 2.74.6-1
ii libgomp1 12.2.0-14
ii libgphoto2-6 2.5.30-1
ii libgphoto2-port12 2.5.30-1
ii libgraphicsmagick-q16-3 1.4+really1.3.40-2
ii libgtk-3-0 3.24.37-2
ii libheif1 1.15.1-1
ii libicu72 72.1-3
ii libimath-3-1-29 3.1.6-1
ii libjpeg62-turbo 1:2.1.5-2
ii libjson-glib-1.0-0 1.6.6-1
ii libjxl0.7 0.7.0-10
ii liblcms2-2 2.14-2
ii liblensfun1 0.3.3-1
ii liblua5.4-0 5.4.4-3
ii libopenexr-3-1-30 3.1.5-4
ii libopenjp2-7 2.5.0-1+b1
ii libosmgpsmap-1.0-1 1.2.0-2
ii libpango-1.0-0 1.50.12+ds-1
ii libpangocairo-1.0-0 1.50.12+ds-1
ii libpng16-16 1.6.39-2
ii libportmidi0 1:217-6.1
ii libpugixml1v5 1.13-0.2
ii librsvg2-2 2.54.5+dfsg-1
ii libsdl2-2.0-0 2.26.4+dfsg-1
ii libsecret-1-0 0.20.5-3
ii libsoup2.4-1 2.74.3-1
ii libsqlite3-0 3.40.1-2
ii libstdc++6 12.2.0-14
ii libtiff6 4.5.0-5
ii libwebp7 1.2.4-0.1
ii libwebpmux3 1.2.4-0.1
ii libx11-6 2:1.8.4-2
ii libxml2 2.9.14+dfsg-1.1+b3
ii libxrandr2 2:1.5.2-2+b1
ii zlib1g 1:1.2.13.dfsg-1

darktable recommends no packages.

darktable suggests no packages.

-- no debconf information

David Bremner

unread,
Apr 17, 2023, 3:50:06 PM4/17/23
to
Michael Below <be...@judiz.de> writes:

> Darktable should take more care in handling its input data. If data (in
> the XMP file?) is broken, darktable should discard the invalid input
> data. Anyhow, no kind of input data should lead darktable to a
> segmentation fault ("Speicherzugriffsfehler").
>
> I am attaching the XMP file.

Can you also provide (somehow, presumably not by email) the RAF file?
I'm afraid static analysis of XMP files is not likely to yield much
information.

Failing that you could try to generate a backtrace; I believe there are
instructions on darktable.org.

d

Michael Below

unread,
Apr 17, 2023, 4:20:04 PM4/17/23
to
Am Montag, dem 17.04.2023 um 22:44 +0300 schrieb Michael Below:
> I will try to send it by separate
> mail.
>
Sorry, it doesn't go through. I will try dropbox or something like that
tomorrow.

Cheers
Michael

Michael Below

unread,
Apr 17, 2023, 4:20:04 PM4/17/23
to
Am Montag, dem 17.04.2023 um 16:22 -0300 schrieb David Bremner:
> Michael Below <be...@judiz.de> writes:
>
> > Darktable should take more care in handling its input data. If data
> > (in
> > the XMP file?) is broken, darktable should discard the invalid
> > input
> > data. Anyhow, no kind of input data should lead darktable to a
> > segmentation fault  ("Speicherzugriffsfehler").
> >
> > I am attaching the XMP file.
>
> Can you also provide (somehow, presumably not by email) the RAF file?
> I'm afraid static analysis of XMP files is not likely to yield much
> information.

It is a family picture (Easter egg hunt), so I do not want to see it in
a public place like the bugtracker, but I'm happy to provide the
picture to you for your own work. I will try to send it by separate
mail.

Michael

Michael Below

unread,
Apr 19, 2023, 7:50:05 AM4/19/23
to
I also filed the issue on github, upstream has also been able to reproduce the issue:

https://github.com/darktable-org/darktable/issues/14241#issuecomment-1514240107

Am 19. April 2023 13:28:19 MESZ schrieb David Bremner <da...@tethera.net>:
>Control: tag -1 confirmed
>I did manage to download the file, and reproduce the segfault. I will
>try to make a decent backtrace and pass the bug upstream.
>
>I attach my first attempt at a backtrace in case it is useful to
>someone. I suspect I need to install a few more debug symbols.
>
0 new messages