tls: fix SecurePair external memory reporting #11896
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ensure that AdjustAmountOfExternalAllocatedMemory() is called when the SecurePair is destroyed. Not doing so is not an actual memory leak but it makes `process.memoryUsage().external` wildly inaccurate and can cause performance problems due to excessive garbage collection.
nodejs-github-bot
added
c++
mscdex
added
memory
jasnell
approved these changes
Mar 17, 2017
addaleax
approved these changes
Mar 19, 2017
Member
Author
|
parallel/test-timers failing on the fedora23 buildbot is probably a flake but just in case: https://ci.nodejs.org/job/node-test-pull-request/6956/ |
Member
|
There was some red in that CI that should be unrelated, but just to be safe: https://ci.nodejs.org/job/node-test-pull-request/6969/ |
jasnell
pushed a commit
that referenced
this pull request
Mar 22, 2017
Ensure that AdjustAmountOfExternalAllocatedMemory() is called when the SecurePair is destroyed. Not doing so is not an actual memory leak but it makes `process.memoryUsage().external` wildly inaccurate and can cause performance problems due to excessive garbage collection. PR-URL: #11896 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
Member
|
New CI was all green. Landed in 86d74a2 |
MylesBorins
pushed a commit
that referenced
this pull request
Mar 28, 2017
Ensure that AdjustAmountOfExternalAllocatedMemory() is called when the SecurePair is destroyed. Not doing so is not an actual memory leak but it makes `process.memoryUsage().external` wildly inaccurate and can cause performance problems due to excessive garbage collection. PR-URL: #11896 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
Merged
Contributor
|
@bnoordhuis v6.x? |
Member
Author
|
@MylesBorins Yes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
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.
Ensure that AdjustAmountOfExternalAllocatedMemory() is called when
the SecurePair is destroyed. Not doing so is not an actual memory
leak but it makes
process.memoryUsage().externalwildly inaccurateand can cause performance problems due to excessive garbage collection.