Add stats to distinguish android renderer crashes.
This CL is a precursor to expanding Clank stability scope
to all OOM protected renderers that crash while Chrome is
in the foreground.
The difference in scope is effectively
the number of renderers that crash as its corresponding
tabs are all backgrounded. This transition time is one second before the OOM protection is dropped. Most,
if not all, such renderer crashes are due to the Android OOM
killer. Overall difference in proposed stability stats will
not be much different, and will be easily seen with the new
histogram.
Expanding scope allows us to have native record which of
the renderer crashes actually results in a minidump file
being generated, thus demystifying whether the renderer
was OOM killed or actually crashed. This native stat can
be made more robust in the future, but this CL paves the
foundation, assuming Tab.RendererExitStatus is comparable
to Tab.RendererCrashStatus.
Review URL: https://codereview.chromium.org/1447213002
Cr-Commit-Position: refs/heads/master@{#361110}
CrOS-Libchrome-Original-Commit: 587e705898fd262f83acd78eef13f5858f73c4e2
3 files changed