fix: process.getProcessMemoryInfo not being exposed to sandbox renderers #17669
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
codebytere
changed the title
|
@codebytere it looks like you have an extra commit in this PR that isn't germane to #17661. |
carterbs
reviewed
Apr 3, 2019
codebytere
force-pushed
the
fix-proc-mem-info
branch
from
ba31a4b
to
f1d5b07
Compare
carterbs
approved these changes
Apr 3, 2019
MarshallOfSound
approved these changes
Apr 3, 2019
|
Release Notes Persisted
|
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.
Description of Change
Fixes #17661.
Exposes
process.getProcessMemoryInfoto sandbox renderers.cc @MarshallOfSound
Checklist
npm testpassesRelease Notes
Notes: Fixed
process.getProcessMemoryInfonot being exposed to sandbox renderers.