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

Issue 644665 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Crash in media::mp4::BoxReader::ScanChildren

Project Member Reported by ClusterFuzz, Sep 7 2016

Issue description

Cc: mmoroz@chromium.org kcc@chromium.org aizatsky@chromium.org
Components: Internals>Media>Video
Owner: strobe@chromium.org
strobe@, as an initial author of the DCHECK we've triggered (https://chromium.googlesource.com/chromium/src/+/8398ac4a8713c7382bdb88ff52c61903690b72bc), would you mind taking a look to tell us: should we ignore that crash or it is a valid issue?

Please feel free to re-assign as needed.
Cc: strobe@chromium.org wolenetz@chromium.org
Owner: chcunningham@chromium.org
over to Chris since Matt is full on ffmpeg :)
Components: Internals>Media>Source
Status: Assigned (was: Untriaged)
Project Member

Comment 5 by sheriffbot@chromium.org, Nov 22 2016

Labels: -Restrict-View-EditIssue
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 6 by ClusterFuzz, Dec 1 2016

ClusterFuzz has detected this issue as fixed in range 428102:428149.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5887923562217472

Fuzzer: libfuzzer_mp4_box_reader_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e900007825
Crash State:
  base::debug::DebugBreak
  media::mp4::BoxReader::ScanChildren
  _start
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=415616:415651
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=428102:428149

Minimized Testcase (0.02 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95iw1IpPA6vl6oWyl2zt_FBWIcrLvlQMYvOUftBLrKF3toJ7CxPKMrBlUxTzh_Ch915t2-0uqD-Tf7RZA8C5XUOlusQxJ-C2C2LEbgZcumvRP2TwdZEJUI8C8poQ65tdBbo0ESnGvPb7LJiUOyHJFX1QeL62w?testcase_id=5887923562217472

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 7 by ClusterFuzz, Dec 1 2016

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

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Hmm. Glancing over the results of the CF verification requested by chcunningham@ (#6), this looks like Dale's fix for crbug 644665 fixed this.  Indeed, this looks like duplicate of 644665. Chris, do you agree?
My clipboard oops. In #8, s/644655/659184/
I agree. I can't promise that Dale's change completely addresses all bugs, but definitely the stack in the initial report is no longer possible.

Sign in to add a comment