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

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 2302683006: [Merge to M53] Task Manager doesn't show the GPU memory of processes on ChromeOS (Closed)

Created:
4 years, 3 months ago by afakhry

Modified:
4 years, 3 months ago

Reviewers:
spang

CC:
chromium-reviews, kalyank, ozone-reviews_chromium.org

Target Ref:
refs/pending/branch-heads/2785

Project:
chromium

Visibility:
Public.

[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) Committed: https://chromium.googlesource.com/chromium/src/+/7b877df656666f0f21b815b45f4c2cf1b718659b

Created: 4 years, 3 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+2 lines, -1 line)			Patch
	M	ui/ozone/platform/drm/host/drm_gpu_platform_support_host.cc	View		1 chunk	+2 lines, -1 line	0 comments	Download

Total messages: 2 (1 generated)

afakhry

4 years, 3 months ago (2016-09-02 21:39:23 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
7b877df656666f0f21b815b45f4c2cf1b718659b (presubmit successful).