Hi,
I experienced a similar issue in the past and it has proven to be
difficult identifying the one image that causes dt to crash.
One idea: a script could use darktable-cli to "probe" each single image
in the last collection. If darktable-cli crashes on a specific image
that one should be put into quarantine.
Ulrich
Am 21.10.2015 um 06:02 schrieb Alexander Rabtchevich:
Hello
Tomorrow dt (from current git) crashed at editing. After it it began
crashing at startup every time. Rebooting and rebuilding didn't help. So
I physically moved all files from the last collection to other
directory, started darktable, removed images from the collection,
returned images to the original directory (all except the bad .xmp file)
and re-imported them. Below is the backtrace output, but I've deleted
the wrong xmp file, so it can be of no help.
Is there a way to detect that situation somehow and overcome it
automatically or with additional program? As I remember, that was not
the first time dt crushed at startup with some bad settings for the last
opened or edited image.
With respect,
Alexander Rabtchevich
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to [email protected]
