Clank's foreground OOM tracking should to be TDI-aware |
||||
Issue descriptionAndroid 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.
,
Jun 14 2017
,
Jun 15 2017
,
May 8 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by creis@chromium.org
, Jun 14 2017