New issue
Advanced search Search tips

Issue 705152 link

Starred by 1 user
Status: Started
Owner:
sande...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Add decode error reporting in media-internals

Project Member Reported by sande...@chromium.org, Mar 24 2017 
Messages from decoders (FFmpeg in particular) should be included in chrome://media-internals so that web developers do not need debug builds to learn the cause of playback failures.
Project Member

Comment 1 by bugdroid1@chromium.org, Mar 27 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b20148e73c9d380f84968dac00dae26425d05b78

commit b20148e73c9d380f84968dac00dae26425d05b78
Author: sandersd <sandersd@chromium.org>
Date: Mon Mar 27 21:00:40 2017

Log AVERROR messages from FFmpegDemuxer in chrome://media-internals.

This uses the same mechanism as was added to allow FFmpegVideoDecoder to convert AVERROR codes into messages, and logs the resulting message at the DEBUG media-log level.

BUG=705152

Review-Url: https://codereview.chromium.org/2771983006
Cr-Commit-Position: refs/heads/master@{#459877}

[modify] https://crrev.com/b20148e73c9d380f84968dac00dae26425d05b78/media/filters/ffmpeg_demuxer.cc
[modify] https://crrev.com/b20148e73c9d380f84968dac00dae26425d05b78/media/filters/ffmpeg_demuxer.h
[modify] https://crrev.com/b20148e73c9d380f84968dac00dae26425d05b78/media/filters/ffmpeg_video_decoder.cc
►

Sign in to add a comment