-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
tls: fix SecurePair external memory reporting #11896
Closed
bnoordhuis
wants to merge
1
commit into
nodejs:master
from
bnoordhuis:fix-securepair-external-memory-reporting
Closed
tls: fix SecurePair external memory reporting #11896
bnoordhuis
wants to merge
1
commit into
nodejs:master
from
bnoordhuis:fix-securepair-external-memory-reporting
Conversation
This file contains 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++
Issues and PRs that require attention from people who are familiar with C++.
crypto
Issues and PRs related to the crypto subsystem.
labels
Mar 17, 2017
mscdex
added
memory
Issues and PRs related to the memory management or memory footprint.
tls
Issues and PRs related to the tls subsystem.
and removed
crypto
Issues and PRs related to the crypto subsystem.
labels
Mar 17, 2017
jasnell
approved these changes
Mar 17, 2017
addaleax
approved these changes
Mar 19, 2017
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/ |
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 <jasnell@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
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 <jasnell@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
Merged
@bnoordhuis v6.x? |
@MylesBorins Yes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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().external
wildly inaccurateand can cause performance problems due to excessive garbage collection.