This repository has been archived by the owner on Feb 16, 2020. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Fixed the EADRRINUSE exception that is thrown when debugging
What is the current behavior? (You can also link to an open issue here)
I see "Child process is died" message alert and EADDRINUSE exception in the console after a child process is started for a process when running the app in debug mode. (same in VS Code and IntelliJ)There are some open discussions in nodejs about this issue. Please see:
debugging and fork (Error: listen EADDRINUSE :::5858) nodejs/node#8495 (comment)
Debugger doesn't work for processes which fork other processes nodejs/node#9435
What is the new behavior (if this is a feature change)?
This is a temporary fix. I think using
cluster
instead ofchild_process
solves the problem as mentioned here debugging and fork (Error: listen EADDRINUSE :::5858) nodejs/node#8495 (comment) and as applied here Use cluster to spawn child-processes. rocjs/roc-package-webpack-node#13