New issue
Advanced search Search tips

Issue 869744 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 852906
Owner:
Closed: Sep 4
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Measure the time elapsed from the low-mem triggered to the first kill of tab/app

Project Member Reported by cywang@chromium.org, Aug 1

Issue description

One solution is to have metric_daemon epoll on the /dev/chromeos-low-mem to write the timestamp to /tmp/uptime-low-mem-triggered. And later, we could read the timestamp from Tab Discarder to get the full latency for the first kill of tab/app.
 
Labels: -Pri-3 M-70 Pri-2
Mergedinto: 852906
Status: Duplicate (was: Untriaged)
The same is traced on crbug/852906 

Sign in to add a comment