Update chrome.processes API to have platform independent metrics |
|||
Issue descriptionOne concern with the current (experimental) chrome.processes API is that the memory metrics are not the same on different platforms. This makes it hard for extensions to interpret the values without checking what platform they're running on (which is unusual for extensions). This was true of CPU metrics as well, until issue 741202 was recently fixed. erikchen's proposal (https://docs.google.com/document/d/1PZyRzChnvkUNUB85Op46aqkFXuAGUJi751DJuB6O40g/edit) should hopefully make this possible.
,
Oct 3 2017
Assigning to you for now, so that you can triage.
,
Oct 3 2017
I don't think Nick was planning to work on this either, so I'm leaving it marked as available. (Nick, feel free to grab it if you disagree.)
,
Oct 4 2017
erikchen@'s Memory Footprint metric (platform independent) appears to have landed in r506220 in issue 771382. That's probably what the chrome.processes API should be updated to use.
,
Aug 28
who in the team can triage and work on this?
,
Aug 28
Our team (Site Isolation) currently has no cycles to work on this API. We are happy to help with consulting for anyone that takes it up! |
|||
►
Sign in to add a comment |
|||
Comment 1 by creis@chromium.org
, Sep 28 2017