At a high-level, we should add any necessary logging/metrics so we can answer the question, "how often do we fail at video playback and what are the top reasons?"
From Hiro:
We have three metrics for HW video decoder.
Media.GpuVideoDecoderInitializeStatus
Media.GpuVideoDecoderError
Media.GpuArcVideoDecodeAccelerator.InitializeResult
First two metrics are for pure Chrome video stack.
The last one is for ARC++ video stack.
But the three metrics Hiro listed don't provide a complete picture, hence filing this bug.
We should add metrics to track video playback failures (in Chrome, ARC++, the media app, etc - for both software and hardware decoding) so we can detect regressions - i.e. we should track if there are any major spikes.
Comment 1 by hiroh@chromium.org
, May 9 2018Status: Duplicate (was: Untriaged)