New issue
Advanced search Search tips

Issue 773804 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: preroll_buffer->timestamp() <= timestamp() in stream_parser_buffer.cc

Project Member Reported by ClusterFuzz, Oct 11 2017

Issue description

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

Fuzzer: libFuzzer_mediasource_MP4_AACLC_AVC_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  preroll_buffer->timestamp() <= timestamp() in stream_parser_buffer.cc
  media::StreamParserBuffer::SetPrerollBuffer
  media::FrameProcessor::HandlePartialAppendWindowTrimming
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=506187:506231

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 
Project Member

Comment 1 by ClusterFuzz, Oct 12 2017

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

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Oct 12 2017

Labels: Test-Predator-AutoOwner
Owner: wolenetz@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/4b857b29abcd5bb55cdbd49755a8c291b37f65da (MSE: Allow negative DTS when MseBufferByPts feature is enabled).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
Project Member

Comment 3 by bugdroid1@chromium.org, Oct 14 2017

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

commit d4bc1bd74b415530b4606fc5fa0011d9d0562a21
Author: Matt Wolenetz <wolenetz@chromium.org>
Date: Sat Oct 14 01:24:24 2017

MSE: Apply more sanity to audio preroll buffer timestamp

An audio preroll frame's timestamp must not be higher than the frame
for which it will preroll. This change prevents such a buffer from being
used as preroll.

BUG= 773804 

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: Icdc9746aa56011389b934715f7182f9c164d3a37
Reviewed-on: https://chromium-review.googlesource.com/720201
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#508902}
[modify] https://crrev.com/d4bc1bd74b415530b4606fc5fa0011d9d0562a21/media/filters/frame_processor.cc

Project Member

Comment 4 by ClusterFuzz, Oct 14 2017

ClusterFuzz has detected this issue as fixed in range 508894:508912.

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

Fuzzer: libFuzzer_mediasource_MP4_AACLC_AVC_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  preroll_buffer->timestamp() <= timestamp() in stream_parser_buffer.cc
  media::StreamParserBuffer::SetPrerollBuffer
  media::FrameProcessor::HandlePartialAppendWindowTrimming
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=506187:506231
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=508894:508912

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 5 by ClusterFuzz, Oct 14 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 4883134134091776 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Cc: dalecur...@chromium.org
Components: -Internals>Media Internals>Media>Source
Labels: M-64
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components
Labels: -Test-Predator-AutoOwner Test-Predator-Auto-Owner

Sign in to add a comment