[Crash] SIGSEGV with unknown origin

Is there an existing issue for this?

• I checked and did not find my issue in the already reported ones

Describe the bug

I was editing a picture when darktable just crashed.
I think I was increasing the highlights (+30 -> +40% or +40% -> +50%, if that is important).

I ran darktable from CLI after it crashed to see if it would log anything, (see full log below; using -d all did also not print any more useful information; logs just stopped for a while before I saw the same crash log line).

Now I can't even open the file anymore without darktable crashing.
I removed the ~/.cache/darktable directory and the .xmp file associated with the edited image, both did not change the outcome at all.

The image has a black box over it in darktable now, I'm not sure where that comes from - might be a mask I added around a lamp that was there.

I can open and edit other images just fine.
The image where the crash occurred has a parametric mask that selects anything that is "almost white" (I think 98.6 to 100 brightness) - maybe that helps. That's also around the area where the black box appears, even if it doesn't line up perfectly.

Steps to reproduce

I don't know.
If you have any idea, what I could try, let me know.

Expected behavior

No response

Logfile | Screenshot | Screencast

darktable_debug.log

^^ It never finishes processing and just crashes after this

Commit

No response

Where did you obtain darktable from?

distro packaging

darktable version

5.4.1

What OS are you using?

Linux

What is the version of your OS?

CachyOS (Arch Linux)

Describe your system

No response

Are you using OpenCL GPU in darktable?

I dont know

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

Start by reviewing the attached darktable_debug.log and the reported parametric-mask scenario. The issue names no source file, entry point, reproducible steps, or test, so determining the crash path will require reproducing it or obtaining more diagnostic data. Done means identifying and fixing the SIGSEGV and adding a regression test or reliable reproduction.