add UMA histogram for OOM kill time |
|||||
Issue descriptionWe want to know how much OOM kills contribute to jank. To do that, we must measure the time between a OOM kill request, and when some OOM kill actually happens (because of delays or "refusals to die"). There are different ways of doing it. One would be to add tracing events at the relevant locations, then use the tracing sysfs to monitor those events. We have to be a little careful because /sys/kernel/debug/tracing already has occasional users (for instance, for performance profiles). We may have to add a "tracing daemon" which would allow us to safely share the trace_pipe output.
,
May 25 2018
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
,
Sep 28
Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.
,
Nov 8
<UI triage> Bug owners, please add the appropriate component to your bug. Thanks!
,
Nov 9
,
Nov 14
Issue 905453 has been merged into this issue.
,
Nov 14
(copied from duplicate issue 905453 ) These logs from issue 896805 demonstrate the problem. <4>[ 212.236266] Task <URL: 13> refused to die (killer <URL: 14> nvcsw=1454, nivcsw=3721) <4>[ 213.311265] Task <URL: 13> refused to die (killer powerd:1349:1349, nvcsw=409, nivcsw=375) <4>[ 213.789207] Task <URL: 13> refused to die (killer powerd:1349:1349, nvcsw=472, nivcsw=379) <4>[ 213.890298] Task <URL: 13> refused to die (killer Chrome_SyncThre:2839:1366, nvcsw=521, nivcsw=762) <4>[ 214.728599] Task <URL: 13> refused to die (killer mali-mem-purge:1639:1606, nvcsw=2227, nivcsw=1514) <4>[ 215.158786] Task <URL: 13> refused to die (killer powerd:1349:1349, nvcsw=522, nivcsw=395) <4>[ 215.618208] Task <URL: 13> refused to die (killer powerd:1349:1349, nvcsw=554, nivcsw=404) <4>[ 218.169292] Task ScriptStreamer :5269 refused to die (killer shill:1547:1547, nvcsw=578, nivcsw=1477) <4>[ 218.377301] Task ScriptStreamer :5269 refused to die (killer TaskSchedulerFo:1585:1366, nvcsw=22372, nivcsw=5696) <4>[ 220.225357] Task CompositorTileW:5247 refused to die (killer Compositor:5345:5334, nvcsw=203, nivcsw=151) The anomaly collector already scans /var/log/messages with a lex-generated scanner, so the overhead of adding more patterns should be low. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ovanieva@chromium.org
, May 25 2018