Repository navigation
Add JOB_OBJECT_LIMIT_BREAKAWAY_OK to CreateKillOnParentExitJob for Windows KillOnParentExit support #129709
Description
Activity
Tagging subscribers to this area: @JulieLeeMSFT, @VSadov
See info in area-owners.md if you want to be subscribed.Tagging subscribers to this area: @dotnet/area-system-diagnostics-process
See info in area-owners.md if you want to be subscribed.- linked a pull request that will close this issueAllow for Job escape when using KillOnParentExit #130032
on Jun 30, 2026 - added a commit that references this issue
on Jun 30, 2026 - added a commit that references this issue
on Jul 15, 2026 - locked and limited conversation to collaborators
on Jul 31, 2026
The killer job created for Windows when
KillOnParentExitis true doesn't include theJOB_OBJECT_LIMIT_BREAKAWAY_OKflag, which means there's no way for a child process to be created outside the job. There are scenarios where an application may need to be able to create a process outside the job to support scenarios like resource cleanup. Please consider updating theCreateKillOnParentExitJobmethod to setJOB_OBJECT_LIMIT_BREAKAWAY_OKon the created job object to allow child processes to be selectively created outside of the job when necessary.