GRC: associate origins instead of URLs with processes |
|||||
Issue descriptionMemory coordinator would like to associate some metadata to attribute memory usage. Currently, that comes in the form a URL, but it might be nicer to have an origin (if we keep with the current design of copying the URL into GRC's shadowed state of the world). I'm told that this needs a privacy review though (so restricting visibility for now, not sure what the requirements around that are). It'll also be important to make sure that passing origins (as URLs) doesn't inadvertently skew some metrics.
,
Jul 26
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
,
Jul 26
chrisha@, has anything changed here? It looks like we're still passing around URLs in a number of places and we still have a process to URL mapping: https://cs.chromium.org/chromium/src/services/resource_coordinator/public/mojom/coordination_unit_introspector.mojom?rcl=17cb8dcddcc0dbbbd2d3d1022f3f5f5d15f0f800&l=27
,
Jul 26
,
Jul 27
Nothing has changed yet, no. However we've come to the painful conclusion that we'd rather not have the "coordination graph" be hosted in a separate service, and that we'd like it to live natively in the browser. We have plans to migrate the code into cr/br/rc Q4ish, so this bug becomes a WontFix in that context. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by erikc...@chromium.org
, Jul 25 2017