-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
inspector-port=0 edge case crash #13499
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
This happens on master as well as 8.x and 8.x-staging |
I do not see this on Linux and Mac. Other then Windows OS, is there anything else that might be triggering it? |
I only tried it on my laptop (Ubuntu), and it repros for me, and makes sense.
|
And when I back out the fix in #13504, the test in that PR fails. |
Oh! I didn't notice it was "--inspect-port" and not just "--inspect"
…On Tue, Jun 6, 2017 at 3:16 PM Sam Roberts ***@***.***> wrote:
And when I back out the fix in #13504
<#13504>, the test in that PR fails.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#13499 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AARkrdFSi_QpM40bsvHiSP4RisxHNhx_ks5sBc-6gaJpZM4Nxl2P>
.
|
Inspector start means that it exists, but doesn't mean it is listening on a port, that only happens if it is doing I/O (i.e. has an io object). PR-URL: nodejs#13504 Fixes: nodejs#13499 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
after 399cb25 there's an edge case that crashes
node
The text was updated successfully, but these errors were encountered: