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

Issue 884021 link

Starred by 3 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature


Participants' hotlists:
GSuite-Priorities


Sign in to add a comment

Expose signal for number of browsing contexts in current process

Project Member Reported by pweis@google.com, Sep 13

Issue description

GSuite apps have observed an increase in memory usage reported via performance.memory with the rollout of site isolation. This is expected, but it would generally be helpful to expose a signal to pages about the number of browsing contexts in the current process together with the memory measurement. This would allow pages to better attribute what portion of memory usage is due to them directly, vs. just being accounted from unrelated similar domain contexts.

Ideally would be able to understand both top-level browsing contexts only, and total number including iframes.

This has been proposed before in the GSuite performance.memory perspective doc: https://docs.google.com/document/d/1Y7KKXVmMY5QFCLh73hleHanmAg5Icu5IgBP7q4LFUYI/edit#bookmark=id.wl8fkv21l476
 
Components: -Blink
Labels: Pri-3
Status: Available (was: Untriaged)
Cc: yoavweiss@chromium.org
@yoav: what do you think we can do about this bug? Could this be discussed
at the WebPerf WG? I see crbug.com/857327 was discussed yesterday.
Cc: u...@chromium.org
There's some overlap here with crbug.com/895966. That FR is about exposing per-frame memory information, but likely will end being bundled per browsing context. If that gets implemented, we would have a (somewhat indirect) signal via the memory API, but think it would still be preferable to have a more direct signal independent of memory metrics as proposed here.

Sign in to add a comment