Suspecting:

Author: dalecurtis
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src//+/39a7f93d67f79d6afadb0f74254eef19b5ff9318
Time: Tue Jul 19 18:34:59 2016
The CL last changed line 45 of file audio_timestamp_validator.cc, which is stack frame 3.

@dalecurtis: Could you please look into this issue.

Thank you.

Looks like it's complaining about the new timestamp validator, but likely ffmpeg is outputing something gnarly.

I think both this and  Issue 628521  are essentially the same... content played with either negative timestamps or no timestamp tripping up DCHECKs. 

One route here would be to replace the DCHECKs in ffmpeg_demuxer with decode errors... WDYT?

ClusterFuzz has detected this issue as fixed in range 408588:408608.

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

Fuzzer: media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e90000013f
Crash State:
  media::AudioTimestampValidator::CheckForTimestampGap
  media::DecoderStreamTraits<
  media::DecoderStream<
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=408389:408457
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=408588:408608

Minimized Testcase (0.60 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97eDURks_S-Lb2ZpOidV9n4qwdLiUUBrxIl122LKV61NzSJXqcsDFPvMdrwhE3qTC-31rujPKDw-0K2inzPzfAYU94EymWmchvU_1b-76B7LQ9pkcUgUcKNi5iMBKfQ59L6AdlE8D-O2nYYkBhNa33UsPlIpA?testcase_id=5167049798320128

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.

ClusterFuzz testcase is verified as fixed, closing issue.

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

No changes from me yet - "fixed" seems unlikely.

Dale, see comment #3

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

For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md.

The link referenced in the description is no longer valid.

(bulk edit)