New issue
Advanced search Search tips

Issue 617415 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Memory & events tracing in mus

Project Member Reported by penghuang@chromium.org, Jun 4 2016

Issue description

In current chrome, we can trace system memory & GPU memory usage for every process. How do we tracing them in mus world?

In current chrome, for GPU memory, every GPU client process has unique tracing ID. The GPU process will use this ID to tracing allocations done on behalf of the connecting process. This so we can correctly attribute memory to the process. This needs to be thought about more generally in the mus design.
 
Components: Internals>MUS
Labels: Proj-Mustash
Components: -Internals>MUS Internals>Services>WindowService
Components: -MUS
Status: WontFix (was: Untriaged)
I believe all this works correctly now.

Sign in to add a comment