The reason for the problem is that when searching for parameters of the specified type and returning values, the fork (or similar function) of child_process enters the run list, and when running in the child thread, the grandchild thread is created.
The search engine filters the impossible function types and then creates a child thread to run all possible functions, including all functions of the child_process module. My project is a function search engine that finds functions that match the conditions based on input and output. In order to make the problem clearer, I will explain my project, this is my project link, currently only a demo: Perhaps some of the clustered child management work in npm modules like adios might be helpful for your review?Īdios seems to be used to establish IPC channels between clusters, and my guess is not applicable to my situation.
It sounds like you have a combination of both of the above occurring!! Could your child processes be forking grandchildren too! (thus, distorting the lifecycle of the child?) Alternatively, should you multi-threaded child process work be conducted with daemon threads? Independent child processes are created through fork/exec on UNIX, accomplishing the action of a spawn as practicised in other OSes. Zombies will persist if the parent does not acknowledge their ending - this is the fork/join model to manage child process creation.
Node js mac kill process code#
Zombie processes are the opposite where a child process ends first before the parent, and will exist only as an entry in the process table for any job (namely the parent) to ascertain its exit code status, which is what is acknowledged (read) during the wait typical behaviour conducted during join. If the parent process terminates first, then the init job (PID 1) will inherit all such orphaned processes. How did you format your output? Mine appears as a wall o' text like this:ĥ02 1128 1125 0 3:17PM ? 0:31.12 /Applications/Reactotron.app/Contents/Frameworks/Reactotron Helper (Renderer).app/Contents/MacOS/Reactotron Helper (Renderer) -type=renderer -field-trial-handle=1718379636,9355752010542677649,1429803248351936294,131072 -disable-features=SpareRendererForSitePerProcess -lang=en-US -app-path=/Applications/Reactotron.app/Contents/Resources/app.asar -node-integration -no-sandbox -no-zygote -background-color=#fff -num-raster-threads=2 -enable-zero-copy -enable-gpu-memory-buffer-compositor-resources -enable-main-frame-before-activation -service-request-channel-token=3685712697854128908 -renderer-client-id=5 -no-v8-untrusted-code-mitigationsĥ02 15785 15718 0 6:18PM ? 0:15.06 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Renderer).app/Contents/MacOS/Code Helper (Renderer) -type=renderer -disable-color-correct-rendering -field-trial-handle=1718379636,9347403567474433047,3772520779013372132,131072 -disable-features=LayoutNG,PictureInPicture,SpareRendererForSitePerProcess -lang=en-US -standard-schemes -secure-schemes=vscode-resource -bypasscsp-schemes -cors-schemes=vscode-resource -fetch-schemes=vscode-resource -service-worker-schemes -app-path=/Applications/Visual Studio Code.What you describe is standard practice for UNIX - not just Linux - where the parent process ends prior to that of the child process.
0 kommentar(er)
