-
Notifications
You must be signed in to change notification settings - Fork 31.1k
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
debugger: fix debugger blocked main thread #5270
Conversation
I don't think blindly closing all handles is the best way to fix this (although it's certainly the easiest) because it introduces memory leaks and corrupts the HandleWrap linked list. #2133 has a solution for cleaning up handles at exit. |
yes, in fact I just want to close tty handle. but will #2133 to be merge? |
Perhaps we can land the cleanup changes. I don't really have time to review it, though. |
@thealphanerd ... any thoughts on this one? |
Nothing off the top of my head. I've assigned it to myself and will investigate |
the test is failing for me locally on osx |
7da4fd4
to
c7066fb
Compare
+1 |
c133999
to
83c7a88
Compare
Is this something we want to try and fix in LTS? |
Possibly. If there is no negative impact then I don't see why not. |
@MylesBorins ... is this still needed? given that the debugger is deprecated and going away, I'm inclined to close |
@jasnell I'm open to closing it... that being said if it can fix 4.x it may be worth it. No one is stepping up to do it though... |
This is a confusing problem, causing debugger not automatically exited. We should fix it |
Feel free to reopen this PR if you get back to working on it. |
see #2110
Call
uv_walk
to close all handles, otherwise would meat error below.