Skip to content

Conversation

@ralfbrown
Copy link
Collaborator

It is possible to get a crash in a background job such as _control_write_sidecars_job_run on exit due to an attempt by the job to check whether the control system is still running with dt_control_running() after darktable.control has been freed. I've experienced this twice since switching my production copy from 5.2.1 to master about three weeks ago.

While this commit is not a total fix, it reduces the vulnerable time window from milliseconds to nanoseconds.

It is possible to get a crash in a background job such as
_control_write_sidecars_job_run on exit due to an attempt by the job
to check whether the control system is still running with
dt_control_running() *after* darktable.control has been freed.

While this commit is not a total fix, it reduces the vulnerable time
window from milliseconds to nanoseconds.
@TurboGit TurboGit added this to the 5.4 milestone Dec 6, 2025
Copy link
Member

@TurboGit TurboGit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@TurboGit TurboGit merged commit 95acdba into darktable-org:master Dec 6, 2025
5 checks passed
@TurboGit TurboGit added the scope: codebase making darktable source code easier to manage label Dec 6, 2025
@ralfbrown ralfbrown deleted the dtcontrol_crash branch December 6, 2025 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

scope: codebase making darktable source code easier to manage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants