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

Issue 629873 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Task Manager shows N/A GPU memory values

Project Member Reported by w...@chromium.org, Jul 20 2016

Issue description

Version: 53.0.2785.13
OS: ChromeOS

What steps will reproduce the problem?
(1) Open Task Manager and make sure  GPU memory is shown.
(2) Runs lots of things!

What is the expected output?

Expect that GPU memory shows each renderer's GPU footprint.

What do you see instead?

GPU memory is always listed as N/A.

 
Screenshot 2016-07-20 at 09.46.30 - Display 1.png
47.0 KB View Download

Comment 1 by w...@chromium.org, Aug 26 2016

Cc: afakhry@chromium.org

Comment 2 by w...@chromium.org, Aug 26 2016

Cc: danakj@chromium.org sadrul@chromium.org fsam...@chromium.org
Labels: -Pri-3 M-53 Pri-2
Bumping priority since this seems to indicate that the GPU process launch logic is not doing what we think it does, under ChromeOS.
Cc: -afakhry@chromium.org
Owner: afakhry@chromium.org
Status: Assigned (was: Untriaged)
I can repo this on ChromeOS but not Linux. I'll take a look.

Comment 4 by w...@chromium.org, Aug 26 2016

Yes, I observed the same thing. I only see missing GPU values if Chrome is
running in a software X server, in which case there is no GPU process to
provide stats for :)
Status: Started (was: Assigned)
CL is up for review: https://codereview.chromium.org/2285983002
Project Member

Comment 7 by bugdroid1@chromium.org, Aug 30 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/77b0dcbf37f91f60f35689c1004802331f949ee0

commit 77b0dcbf37f91f60f35689c1004802331f949ee0
Author: afakhry <afakhry@chromium.org>
Date: Tue Aug 30 06:29:04 2016

Task Manager doesn't show the GPU memory of processes on ChromeOS

On ozone platforms, the message GpuHostMsg_VideoMemoryUsageStats used to be
skipped and not handled. Hence the task manager never received those stats.

BUG= 629873 
TEST=manually open the task manager and show the GPU memory column. Data should be there

Review-Url: https://codereview.chromium.org/2285983002
Cr-Commit-Position: refs/heads/master@{#415224}

[modify] https://crrev.com/77b0dcbf37f91f60f35689c1004802331f949ee0/ui/ozone/platform/drm/host/drm_gpu_platform_support_host.cc

Labels: Merge-Request-53

Comment 9 by dimu@chromium.org, Aug 31 2016

Labels: -Merge-Request-53 Merge-Review-53 Hotlist-Merge-Review
[Automated comment] Less than 2 weeks to go before stable on M53, manual review required.
Labels: -Merge-Review-53 Merge-Approved-53
Approving merge to M53 cros. afakhry@ Please merge this in asap.
Project Member

Comment 11 by bugdroid1@chromium.org, Sep 2 2016

Labels: -merge-approved-53 merge-merged-2785
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7b877df656666f0f21b815b45f4c2cf1b718659b

commit 7b877df656666f0f21b815b45f4c2cf1b718659b
Author: Ahmed Fakhry <afakhry@google.com>
Date: Fri Sep 02 21:35:04 2016

[Merge to M53] Task Manager doesn't show the GPU memory of processes on ChromeOS

On ozone platforms, the message GpuHostMsg_VideoMemoryUsageStats used to be
skipped and not handled. Hence the task manager never received those stats.

TBR=spang@chromium.org
BUG= 629873 
TEST=manually open the task manager and show the GPU memory column. Data should be there

Review-Url: https://codereview.chromium.org/2285983002
Cr-Commit-Position: refs/heads/master@{#415224}
(cherry picked from commit 77b0dcbf37f91f60f35689c1004802331f949ee0)

Review URL: https://codereview.chromium.org/2302683006 .

Cr-Commit-Position: refs/branch-heads/2785@{#817}
Cr-Branched-From: 68623971be0cfc492a2cb0427d7f478e7b214c24-refs/heads/master@{#403382}

[modify] https://crrev.com/7b877df656666f0f21b815b45f4c2cf1b718659b/ui/ozone/platform/drm/host/drm_gpu_platform_support_host.cc

Status: Fixed (was: Started)
Status: Verified (was: Fixed)

Sign in to add a comment