Crash in darkroom about darktable HOT 11 OPEN

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

from darktable.

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.

from darktable.

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?

from darktable.

Likely -d pipe -d verbose -d opencl

from darktable.

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

from darktable.

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

from darktable.

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:

from darktable.

Sorry, don't understand Your question

from darktable.

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.

from darktable.

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 :-)

from darktable.

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

from darktable.