Skip to content
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

src: enable more detailed memory tracking #21742

Closed
wants to merge 3 commits into from

Conversation

addaleax
Copy link
Member

Splitting out from #21741:

This will enable more detailed heap snapshots based on
a newer V8 API.

This commit itself is not tied to that API and could
be backported.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

@addaleax addaleax added memory Issues and PRs related to the memory management or memory footprint. backport-requested-v8.x labels Jul 10, 2018
@nodejs-github-bot nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. lib / src Issues and PRs related to general changes in the lib or src directory. labels Jul 10, 2018

void MemoryTracker::Track(const MemoryRetainer* value) {
v8::HandleScope handle_scope(isolate_);
value->MemoryInfo(this);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just thinking... some trace event output in here might be interesting from a diagnostics point of view... not necessarily in this PR, but at some point.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could probably do that but I’m not sure what to track here – this is static information, not something event-related? We could maybe track the heap dump in progress, but that is already a diagnostic tool by itself

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll play around with it to see if we can get some interesting data out of it after this lands :-)

@addaleax addaleax force-pushed the heap-bp branch 2 times, most recently from 82c79fe to 5641d0e Compare July 11, 2018 16:23
@jasnell
Copy link
Member

jasnell commented Jul 12, 2018

addaleax added 3 commits July 13, 2018 14:40
This will enable more detailed heap snapshots based on
a newer V8 API.

This commit itself is not tied to that API and could
be backported.
@addaleax
Copy link
Member Author

Trying something else to hopefully make MSVC happy: https://ci.nodejs.org/job/node-test-pull-request/15844/

@addaleax
Copy link
Member Author

Windows re-run, this time it looks like it’s just a flake: https://ci.nodejs.org/job/node-test-commit-windows-fanned/19268/

@addaleax addaleax added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Jul 13, 2018
@addaleax
Copy link
Member Author

Nice, Windows re-run came back good. Will land this soon if there are no objections.

@addaleax
Copy link
Member Author

Landed in 57e3015

@addaleax addaleax closed this Jul 13, 2018
addaleax added a commit that referenced this pull request Jul 13, 2018
This will enable more detailed heap snapshots based on
a newer V8 API.

This commit itself is not tied to that API and could
be backported.

PR-URL: #21742
Reviewed-By: James M Snell <jasnell@gmail.com>
@addaleax addaleax deleted the heap-bp branch July 13, 2018 18:02
targos pushed a commit that referenced this pull request Jul 14, 2018
This will enable more detailed heap snapshots based on
a newer V8 API.

This commit itself is not tied to that API and could
be backported.

PR-URL: #21742
Reviewed-By: James M Snell <jasnell@gmail.com>
@targos targos mentioned this pull request Jul 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. c++ Issues and PRs that require attention from people who are familiar with C++. lib / src Issues and PRs related to general changes in the lib or src directory. memory Issues and PRs related to the memory management or memory footprint.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants