New issue
Advanced search Search tips

Issue 714730 link

Starred by 1 user
Status: Fixed
Owner:
wolenetz@chromium.org
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Emit MEDIA_LOG(ERROR) when ffmpeg_audio_decoder encounters unsupported channel change

Project Member Reported by wolenetz@chromium.org, Apr 24 2017 
See  bug 705038 

Having a MEDIA_LOG(ERROR) for this case would have lessened need for using a Chrome Debug build with logging to investigate the root cause of  bug 705038 .

Comment 1 by wolenetz@chromium.org, Apr 24 2017 

CL out for review @ https://codereview.chromium.org/2835043004/
Project Member

Comment 2 by bugdroid1@chromium.org, Apr 24 2017 

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

commit 854dede8e4cb7885e803e9e7f3223f00e89a6d38
Author: wolenetz <wolenetz@chromium.org>
Date: Mon Apr 24 22:01:07 2017

MEDIA_LOG FFmpegAudioDecoder::ConfigureDecoder() channel mismatch

 Bug 705038  encountered a case where such channel mismatch occurred, but
logs were insufficient in a release build. This change makes a previous
DLOG instead do a MEDIA_LOG(ERROR) for this specific case.

BUG= 714730 , 705038 

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

[modify] https://crrev.com/854dede8e4cb7885e803e9e7f3223f00e89a6d38/media/filters/ffmpeg_audio_decoder.cc

Comment 3 by wolenetz@chromium.org, Apr 24 2017

Status: Fixed (was: Assigned)
►

Sign in to add a comment