New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 809651 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

PA and v8 MDPs report the wrong numbers on macOS.

Project Member Reported by erikc...@chromium.org, Feb 6 2018

Issue description

Repro steps:

1) Open a tab to youtube.com. PLay a video.
2) Open a tab to chrome://tracing. Take a memory-infra trace.
3) Run "vmmap -v -interleaved <pid>" in a terminal
4) Open a tab to chrome://tracing. Take a memory-infra trace.

Observations:
In (2) and (4), memory-infra reports 40MB v8, 13MB PA.
In (3), vmmap reports 69MB dirty pages of "Memory tag 254", which is only used by PA and v8. 

I'll continue to dig to see what's going on.
 
trace_youtube11.json.gz
237 KB Download
trace_youtube12.json.gz
261 KB Download
Cc: haraken@chromium.org
Part of the problem is that recent changes made more PartitionAllocatorGenerics [https://chromium-review.googlesource.com/c/chromium/src/+/853120], 

but did not update the PartitionAllocator MDP:
https://cs.chromium.org/chromium/src/third_party/WebKit/Source/platform/wtf/allocator/Partitions.cpp?type=cs&l=131




Cc: erikc...@chromium.org
Owner: bbudge@chromium.org
The rest of the difference is accounted for by the fact that oilpan uses the allocator from partition alloc, which takes the memory regions as 254.

Over to bbudge to fix the MDP bug.

Comment 3 by bbudge@chromium.org, Feb 15 2018

Status: Fixed (was: Assigned)

Sign in to add a comment