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

Issue 714826 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
vmi...@chromium.org
ericrk@chromium.org
ccameron@chromium.org
█ nduca@chromium.org
█ shrike@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Reduce GPU memory usage when Chrome is not "visible".

Project Member Reported by erikc...@chromium.org, Apr 24 2017 
Repro steps:

1) Run Chrome on a machine with multiple virtual desktops.
2) Run "sudo vmmap -v -interleaved <pid>" on the GPU process to measure GPU memory usage.
3) Switch to a virtual desktop with no Chrome windows.
4) Run (2) again.

I expect GPU memory usage to significantly drop, since there's no contents showing. 
test is the output from (2)
test2 is the output from (4)

Instead, there's barely any change at all. I wonder if in general, we're failing to discard memory that we could be discarding from non-visible Chrome Windows.

Comment 1 by ericrk@chromium.org, Apr 24 2017 

From what I understand we don't consider windows that are on non-primary desktop (or maybe even minimized) as not-visible. The only things that are not visible are backgrounded tabs (tabs in a window that are not the foreground tab). This is definitely a problem on Linux as well.

In general, we could do better here, but there are also things to be careful of - should the window still display live updates when swiping into expose mode?

I assume that this is broader than graphics memory (I expect this to be the same signal as passed to blink/v8 for background. If not, we should unify these signals.

Comment 2 by enne@chromium.org, May 5 2017

Cc: ojan@chromium.org
Status: Available (was: Untriaged)
Project Member

Comment 3 by sheriffbot@chromium.org, May 7 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by ojan@chromium.org, May 8 2018

Cc: -ojan@chromium.org

Comment 5 by reve...@chromium.org, Jun 1 2018

Status: Available (was: Untriaged)
►

Sign in to add a comment