You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Shortly after starting darktable I opened an image which had filmic rgb enabled. I disabled it and wanted to enable sigmoid, when darktable crashed. Whether the click to turn sigmoid on already took effect or not, I do not know.
I have not reproduced this yet; I'm uploading the backtrace before I lose it, I'll try to trigger it again later.
Steps to reproduce
I'll try to find the exact sequence. I've now tried enabling/disabling filmic and sigmoid with rapid clicks, but the crash has not re-occurred yet.
Pascal, I have not done much editing, but during that time the crash did not re-occur. Therefore, I am unable to verify the fix with any certainty. Thanks for investigating and publishing the PR so quickly.
Describe the bug
Shortly after starting darktable I opened an image which had filmic rgb enabled. I disabled it and wanted to enable sigmoid, when darktable crashed. Whether the click to turn sigmoid on already took effect or not, I do not know.
I have not reproduced this yet; I'm uploading the backtrace before I lose it, I'll try to trigger it again later.
Steps to reproduce
I'll try to find the exact sequence. I've now tried enabling/disabling filmic and sigmoid with rapid clicks, but the crash has not re-occurred yet.
Expected behavior
should not crash
Logfile | Screenshot | Screencast
darktable_bt_YZ37I2.txt
Commit
No response
Where did you obtain darktable from?
self compiled
darktable version
4.7.0+509~g55b95bb480
What OS are you using?
Linux
What is the version of your OS?
Ubuntu 23.10
Describe your system?
64 GB RAM, Ryzen 5
Are you using OpenCL GPU in darktable?
Yes
If yes, what is the GPU card and driver?
NVidia 1060/6GB, 525.147.05
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
Build type: Release
The text was updated successfully, but these errors were encountered: