Darktable 5.6 crashing in one folder of photos. Is this a known bug?

I’ve been having issues with 5.6 running slowly, which I understand is a known bug that will hopefully be fixed with the next update. (Is there a way to be notified whenever 5.6.1 releases?)

Just today I was going through an older folder looking to re-edit some pictures now that I’m more skilled than I was then, and darktable crashes consistently about halfway through the problem folder. Is there a known fix? Would it be helpful if I could somehow share a log of the crash?

I searched and found someone with a similar problem a year ago but the advice seemed like it was geared toward linux. I’m on windows 11.

thanks.

If you have a github account you can tell github to notify you upon release:

2 Likes

1.) sounds like maybe a file of that folder might be corrupted? Does dt always crash on the same photo?

2.) logs are always a good idea: open powershell, run darktable with "C:\your\installation\path\bin\darktable.exe" -d common and a logfile will be written to Documents\darktable.

1 Like

1.) yes, it does seem to crash beyond a certain photo in that folder

2.) I’m not sure how to read this but here is the log after a crash
darktable-log.txt (71.3 KB)

hm - do you know if that “crashing photo” has a watermark or similar text-module activated, applying a special font / font size (11.7pt it seems)? It’s just a guess, because the log shows “missing font” messages prior to an exception, which might be the cause for the crashing.

21:02:50.954: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
couldn't load font "monospace Condensed Not-Rotated 11.7", falling back to "Sans Condensed Not-Rotated 11.7", expect ugly output.
couldn't load font "Sans Condensed Not-Rotated 11.7", falling back to "Sans Not-Rotated 11.7", expect ugly output.
couldn't load font "monospace Condensed Not-Rotated 11.7", falling back to "Sans Condensed Not-Rotated 11.7", expect ugly output.
couldn't load font "Sans Condensed Not-Rotated 11.7", falling back to "Sans Not-Rotated 11.7", expect ugly output.

You may look into the related XMP sidecar (e.g. using notepad++ since you are on Win 11) and change the font size therein to a normal size, e.g. 11 instead of 11.7, just to see if this solves the problem? If you like XML syntax highlighting, you may add the XML-Tools plugin in notepad++ via plugin-manager…

Edit 1: just saw, that the part of the log I referenced to is outdated, the current exception rises after font messages (size 13pt) and then Magick being the failing component, as far as I understand the output.

Sorry, for not being a big help here.

Edit 2: found this issue (quite old, but points to GPU driver problems), so perhaps you may simply try by starting darktable without OpenCL (i.e. darktable.exe --disable-opencl), if you are using OpenCL on your system…

While I wouldn’t call myself tech illiterate, this might be a tad beyond me. To run darktable without opencl, would I do that via powershell/command prompt?

I did check, and my gpu driver updated yesterday. Would that be a potential culprit?

Unlikely it is opencl

Take half the images/xmp and copy them to a new folder. Import those, if it crashes, then the problem image is in that half, otherwise it is in the other. Keep doing this with half until you find the culprit.

Yes, like you did for generating the log, i.e. open the powershell or cmd, then cd to the darktable installation directory (e.g. cd %programfiles%\darktable) and launch darktable with darktable.exe --disable-opencl