-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
child_process: fork() from -e does not exit #3574
Labels
child_process
Issues and PRs related to the child_process subsystem.
Comments
bnoordhuis
added
the
child_process
Issues and PRs related to the child_process subsystem.
label
Oct 28, 2015
It's a fork bomb!
|
Confirmed on Node 0.6.21-pre too.. It's possible that there's never been a release with a version of |
bnoordhuis
added a commit
to bnoordhuis/io.js
that referenced
this issue
Oct 29, 2015
Remove the `-e` argument from process.execArgv in child_process.fork() to keep `node -e 'require("child_process").fork("empty.js")'` from spawning itself recursively. Fixes: nodejs#3574 PR-URL: nodejs#3575 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]>
bnoordhuis
added a commit
that referenced
this issue
Nov 7, 2015
Remove the `-e` argument from process.execArgv in child_process.fork() to keep `node -e 'require("child_process").fork("empty.js")'` from spawning itself recursively. Fixes: #3574 PR-URL: #3575 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]>
bnoordhuis
added a commit
that referenced
this issue
Nov 30, 2015
Remove the `-e` argument from process.execArgv in child_process.fork() to keep `node -e 'require("child_process").fork("empty.js")'` from spawning itself recursively. Fixes: #3574 PR-URL: #3575 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]>
bnoordhuis
added a commit
that referenced
this issue
Dec 4, 2015
Remove the `-e` argument from process.execArgv in child_process.fork() to keep `node -e 'require("child_process").fork("empty.js")'` from spawning itself recursively. Fixes: #3574 PR-URL: #3575 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]>
bnoordhuis
added a commit
that referenced
this issue
Dec 17, 2015
Remove the `-e` argument from process.execArgv in child_process.fork() to keep `node -e 'require("child_process").fork("empty.js")'` from spawning itself recursively. Fixes: #3574 PR-URL: #3575 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]>
bnoordhuis
added a commit
that referenced
this issue
Dec 23, 2015
Remove the `-e` argument from process.execArgv in child_process.fork() to keep `node -e 'require("child_process").fork("empty.js")'` from spawning itself recursively. Fixes: #3574 PR-URL: #3575 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From here:
parallel/test-child-process-fork3
does the same thing from a file and works fine. Dropping the 'exit' listener doesn't make a difference. @Trott points out that this goes back to at least v0.8.28.The text was updated successfully, but these errors were encountered: