Crash in darkroom

[kofa73]

Describe the bug

I was working in the darkroom (either adjusting the perspective correction module or the contrast in filmic rgb), when darktable crashed. The backtrace file was empty; all I have is the console log from darktable -d pipe (that was the option I used the log a previous crash).
Today I edited many other files the same way, from the same camera, without a crash, so I think it won't be deterministic.

Steps to reproduce

Get the raw and the sidecar from https://tech.kovacs-telekes.org/files/2024-05-20-darktable-crash/

Expected behavior

No response

Logfile | Screenshot | Screencast

console.log

Where did you obtain darktable from?

self-compiled

darktable version

4.7.0+1257~g156a42d33a

What OS are you using?

Linux

What is the version of your OS?

Ubuntu 23.10

Describe your system?

Ryzen 5 5600X

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

NVIDIA GeForce GTX 1060 6GB; 535.171.04

[wpferguson]

Couldn't reproduce with darktable 4.7.0+1271~gf98eda41f0 on 22.04 (gcc 12.3, nvidia 3070)

[jenshannoschwalm]

In the provided log we miss the "got details mask" ... could be the buffer data is wrong in this case or scaling/distorting of the mask failed. BTW no problem here so far.

[kofa73]

Thanks for looking into this.

• This is the 2nd time my backtrace is empty. What could I do to prevent that?
• What -d flags would provide the most useful output?

[jenshannoschwalm]

Likely -d pipe -d verbose -d opencl

[ralfbrown]

Given the choice between perspective and filmic, the fact that the pipe was running in fast mode indicates you were in perspective correction.

[jenshannoschwalm]

Yes, the perspective correction module was open/active. Still the processing was in diffuse and as some lines above would require the detail mask. This point was not reached so one idea would be the distorting of the detail mask somehow failed, the single modules distorting it including their roi would be shown via the -d verbose option

[kofa73]

Could it be related that if rotate and perspective is active, things like filmic's automatic exposure offset selector brings up a rectangle that is offset from the image edges? E.g. (this is another image, but I saw this for all that I recently edited):

If I disable crop, it looks like this:

[jenshannoschwalm]

Sorry, don't understand Your question

[kofa73]

Since it seems the filmic auto-picker area is off (it does not seem to handle the distortion introduced by rotate and perspective), maybe there's some other code that also does not handle it, leading to the crash.

[jenshannoschwalm]

Ah, got it. Likely the data calculated in filmic are not "best" but that should not be a problem.

Took you image and could not reproduce at all, would love a -d pipe -d verbose log :-)

[kofa73]

I'll share the logs when I encounter the next crash.