darktable segfault perhaps related to local copies
originally believed related to rotating image, but it appears
to only happen when working with local copies of remote files.
ref Bug #12409
opened new bug report per request from Pascal Obry
appears to be directly related to using local copy
working on non-local copies does not crash
several segfaults reported on irc/#darktable
latest attached, others:
from darix' builds but crashes when opened. from irc/#darktable 2-12-18:
15:47:08 LebedevRI | also, everything glib is just completely broken by design, so i think │ | "ASAN_OPTIONS=check_initialization_order=1" just completely does not work
#2 Updated by Pascal Obry about 1 year ago
We will need more information. I created 12 local copies. Exited dt and restarted it.
I then created spots, did lot of rotations from darkroom and moved the spots around and again some rotations.
No issue, no crash... So sounds like an issue on your side. Memory? OpenCL? The local copies sounds like a red-herring to me.
#3 Updated by Patrick Shanahan about 1 year ago
ok, perhaps it is really a local issue. I have worked for several
days w/o it happening again. I will try things today that caused
it to happen to me and try to repeat.
I vacuumed and did integrety_check against both data.db and library.db
successfully and purged non-existing images (had 3). I now see only
one unexpected issue:
darktable on startup always reports "1 local copy has been
synchronized" but I have nothing copied locally and I see no
jpg's, orf's or nef's in ~/.cache/darktable/ and I would have