Adding child processes to job objects prevents them from creating job objects of their own
See original GitHub issueWe are hitting an issue while trying to test AspNetCore Module for IIS Express on Windows 7/2008R2 after taking and SDK with https://github.com/dotnet/cli/pull/10720 change.
In the test, we start IIS Express process that spawns new indstance of dotnet.exe, tries to attach it to a job object and fails because the entire process tree is already attached to the job object that CLI has created.
I see couple possible solutions:
- Disable process tracking using job objects on Windows 7
- Set
JOB_OBJECT_LIMIT_BREAKAWAY_OK
flag set on the job object.
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Windows API Job Objects: Don't pass on to grandchildren
1 Answer. You just need to to set the JOB_OBJECT_LIMIT_SILENT_BREAKAWAY_OK flag on the job. This flag prevents child processes from being ...
Read more >Job Objects - Win32 apps
A job object allows groups of processes to be managed as a unit. Job objects are namable, securable, sharable objects that control ...
Read more >Jobfile & Tasks — pyATS Documentation - DevNet
Each task is always encapsulated in its own child process. The combined tasks in the same jobfile always share the same system resources,...
Read more >Node.js Child Processes: Everything you need to know
There are four different ways to create a child process in Node: spawn() , fork() , exec() , and execFile() . We're going...
Read more >How To Launch Child Processes in Node.js
You'll finish by using fork() to create a child process of another Node.js program that you can communicate with as it's running.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The fix to limit the job object usage to Windows 8+ is now in master, which is currently our preview 4 branch. The change will need to propagate through to
dotnet/core-sdk
before it is available in a build.I’ll get that fix ready.