Crash: Have an image + XMP file. DT crashes when it renders it. about darktable HOT 11 CLOSED

you opened the issue and YOU can close it. I cannot.

from darktable.

I see the xmp, is the raw available?

from darktable.

I had to trim it because of the 65535 character limit.

better add such long logs as text file ;)

from darktable.

None of the thread backtraces look like they have anything to do with image processing (either pixels or metadata). In fact, the only two threads which appear to have actually been active at the time of the crash are 2 and 77. Can you post the backtrace for thread 2?

Also, can you try running darktable-cli on the image? That would help narrow down pixel processing versus some other issue since it will render the image but not try to display the result.

darktable-cli M1280255.ORF M1280255.ORF.xmp test.jpg --core -d perf

(The -d perf will let us know where in the pixelpipe it crashed, if it crashes)

from darktable.

Sorry, I could not attach the logfile - perhaps because I attachted the XMP already.

This link contains the full log file, the raw and the xmp. Please let me know if you have it, I will disable it afterwards.

https://cloud.farside.nl/s/ezjZb86WbJPm2S4

from darktable.

Here's the output from

darktable-cli M1280255.ORF M1280255.ORF.xmp test.jpg --core -d perf

darktable_bt_54T0F2 with core d perf command.txt

from darktable.

I see you have found the files. Can you reproduce the issue?

from darktable.

your photo with xmp loads fine for me in dt master
I see no problem with nvidia vidio

trying with intel video. brb

from darktable.

works ok for me on intel video card also

but I am running master, not 4.4.2

from darktable.

Ok, if it can't be reproduced, please close the issue.
I can solve it by deleting the XMP file and doing the edit again.
Thanks a lot for looking in to it, but please don't spend anymore time if it can't be reproduced.

from darktable.

On the darktable-cli backtrace, I see a crash in retouch from within the OpenCL version of the wavelet decomposition (dwt_decompose_cl). So likely the .xmp had corrupted settings for one of the layer edits, or while editing you managed to take some settings beyond what the code can handle.

from darktable.