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

Issue 733383 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Clank's foreground OOM tracking should to be TDI-aware

Project Member Reported by lukasza@chromium.org, Jun 14 2017

Issue description

Android OS can kill renderer processes.  Clank tries to separately track OOM kills that affect foreground VS background content.  Existing metrics are described in go/clank-renderer-oom (google internal only - sorry).

We should try tweaking the metrics, so it is possible to distinguish foreground OOM kill that 1) affects the main page content VS 2) affects only secondary/TDI content.

Having such tweaked metrics is probably a prerequisite for running a TDI trial on Android.
 

Comment 1 by creis@chromium.org, Jun 14 2017

Labels: Proj-TopDocumentIsolation

Comment 2 by wnwen@chromium.org, Jun 14 2017

Cc: yfried...@chromium.org agrieve@chromium.org
Cc: mariakho...@chromium.org

Comment 4 by ojan@chromium.org, May 8 2018

Cc: -ojan@chromium.org

Sign in to add a comment