| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
|
Relaunched CI: https://ci.nodejs.org/job/node-test-commit/3765/. Looks green. PTAL @nodejs/diagnostics. |
Sorry, something went wrong.
There was a problem hiding this comment.
The ASSERT_NE is useless now (and should have been a CHECK_EQ in hindsight.)
Sorry, something went wrong.
There was a problem hiding this comment.
Removed. Thanks!
Sorry, something went wrong.
In some cases close callback was called twice, while in some cases the memory was still not released at all.
|
LGTM |
Sorry, something went wrong.
Sorry, something went wrong.
In some cases close callback was called twice, while in some cases the memory was still not released at all. PR-URL: #7268 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
In some cases close callback was called twice, while in some cases the memory was still not released at all. PR-URL: #7268 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
This change only touches inspector connection
Description of change
In some cases close callback was called twice while other codepaths ended up
not releasing the memory at all.
CC: @ofrobots