New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 823592 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: has_audio || has_video in media_web_contents_observer.cc

Project Member Reported by ClusterFuzz, Mar 20 2018

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5411008961839104

Fuzzer: inferno_flicker
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  has_audio || has_video in media_web_contents_observer.cc
  content::MediaWebContentsObserver::OnMediaPlaying
  void IPC::DispatchToMethodImpl<content::MediaWebContentsObserver, void
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=524986:524992

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5411008961839104

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by ClusterFuzz, Mar 20 2018

Labels: Test-Predator-Auto-Owner
Owner: mlamouri@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/7b74ab4850b0115a996f0076733bc90fc7f8a273 (Autoplay: enable unified policy by default on trunk.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Project Member

Comment 2 by ClusterFuzz, Mar 20 2018

Components: Internals>Core Internals>Media
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
The test allows the file to play as autoplay muted in which case we override the availability of audio track to false. My best guess is that the video track is corrupted.

ffmpeg tells me this about the file:
```
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x559d5227a300] Sample size 2147483798 is too large
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x559d5227a300] Sample size 2147484066 is too large
[h264 @ 0x559d5227bc20] sps_id 0 out of range
[h264 @ 0x559d5227bc20] SPS decoding failure, trying again after escaping the NAL
[h264 @ 0x559d5227bc20] sps_id 0 out of range
[h264 @ 0x559d5227bc20] Decoding pps 0 from avcC failed
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x559d5227a300] Failed to open codec in avformat_find_stream_info
[h264 @ 0x559d5227bc20] sps_id 0 out of range
[h264 @ 0x559d5227bc20] SPS decoding failure, trying again after escaping the NAL
[h264 @ 0x559d5227bc20] sps_id 0 out of range
[h264 @ 0x559d5227bc20] Decoding pps 0 from avcC failed
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'flicker-mp4-3f39b773466c8aad7621d00d36c0706677221d1c1521401315.04.mp4':
  Metadata:
    major_brand     : qt  
    minor_version   : 512
    compatible_brands: qt  
    creation_time   : 1970-01-01T00:00:00.000000Z
    encoder         : Lavf52.40.0
    encoder-eng     : Lavf52.40.0
  Duration: 00:02:56.72, start: 0.000000, bitrate: 279 kb/s
    Stream #0:0(eng): Video: h264 (avc1 / 0x31637661), none, 480x360, 25 fps, 25 tbr, 25 tbn, 50 tbc (default)
    Metadata:
      creation_time   : 1970-01-01T00:00:00.000000Z
      handler_name    : VideoHandler
    Stream #0:1(eng): Audio: mp3 (.mp3 / 0x33706D2E), 44100 Hz, stereo, s16p, 128 kb/s (default)
    Metadata:
      creation_time   : 1970-01-01T00:00:00.000000Z
      handler_name    : DataHandler
```

I will investigate further.
Status: Started (was: Assigned)
I was able to reproduce by setting an audio file on a <video autoplay muted>, see https://mounirlamouri.github.io/sandbox/bugs/823592.html

We should forbid autoplay muted if there is no video track.
Cc: slangley@chromium.org sashab@chromium.org mlamouri@chromium.org dalecur...@chromium.org noel@chromium.org weifangsun@chromium.org
 Issue 820658  has been merged into this issue.
Project Member

Comment 6 by ClusterFuzz, Apr 8 2018

Status: WontFix (was: Started)
ClusterFuzz testcase 5411008961839104 is flaky and no longer crashes, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Sign in to add a comment