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

Issue 770857 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

BrowserGpuMemoryBufferManager creates dumps for unmapped memory

Project Member Reported by ssid@chromium.org, Oct 2 2017

Issue description

Background context: go/memory-infra

Forked from issue 770712.

lalitm@ says:

It seems like the SharedMemoryTracker only tracks memory when shared memory is mapped into the address space of the process and NOT when it is simply created. However, the key point is that some classes like BrowserGpuMemoryBufferManager sometimes only create the address space and then add an edge indicating that the memory is mapped.
 

Comment 1 by ssid@chromium.org, Oct 2 2017

The issue is that the SharedMemoryTracker only creates dumps for mapped memory and we end up with edges to non-existent targets since the tracker does not create dumps.

Eric, is it something we can fix in the gpu provider? Or do we need to create SHM dumps and make size 0?
Status: Assigned (was: Untriaged)

Sign in to add a comment