inspector: proper error message on port collision #4514
Merged
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.
Minimal fix to avoid panicking.
Node allows multiple sessions on different ports, and it is useful under certain scenarios. I don't think a global mutex for single inspector session is the right way to go.
Besides 9229, it seems to me that 9222 is also a common port to use and appears by default. You can also add new ports for Chrome inspector detection.
cc @ry