providing findit results for internal purpose:
Suspected CLs	Findit could not determine the memory tool from the stacktrace. Is it in a new format?

seeing some changes to ffmpeg_demuxer.cc in https://chromium.googlesource.com/chromium/src/+/f25ceedfcb1e403c96eb80702cd29aa1dc370619

servolk @, Could you please check the above issue & help us in finding an owner it its not yours.

Hmm, my change shouldn't have any effect on how we handle buffer timestamps in the FFmpegDemuxer. I think Dale might know more about this, since he added the fixup_negative_timestamps_ in FFmpegDemuxer (https://chromium.googlesource.com/chromium/src/+/aa958fd3a80afdfdc2f747a819a1c67605c637e6).
Dale, any ideas why fuzzing crashes/CHECKs on negative timestamps in FFmpegDemuxer? Do we need to handle negative timestamps in webm in addition to ogg containers?

There should not be negative timestamps in non-ogg containers, so this seems like a bug; though aside from glitchy rendering there is no impact of this behavior beyond the check failure.

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

Fuzzer: media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e90000745f
Crash State:
  media::FFmpegDemuxerStream::EnqueuePacket
  media::FFmpegDemuxer::OnReadFrameDone
  void base::internal::FunctorTraits<void
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=408389:408457

Minimized Testcase (2.16 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95UoK5qCplbg5CW8yxh0ZT7VG9qsLVyRGPkOrzNSq4qMp7kY_2t_BoNWqPVuDDaGW0Tvc6WLL2Z7ic91iSlMvc0uB3fCm9fDEjWQnH1DNYYgEsZvB38O636uD0HoNQQ_pe8sGq9Cf_-T-lmxE0okCWfDcloGQ?testcase_id=6684308601569280

Filer: rnimmagadda

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

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

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

Fuzzer: media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e90000745f
Crash State:
  media::FFmpegDemuxerStream::EnqueuePacket
  media::FFmpegDemuxer::OnReadFrameDone
  void base::internal::FunctorTraits<void
  
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 (2.16 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95UoK5qCplbg5CW8yxh0ZT7VG9qsLVyRGPkOrzNSq4qMp7kY_2t_BoNWqPVuDDaGW0Tvc6WLL2Z7ic91iSlMvc0uB3fCm9fDEjWQnH1DNYYgEsZvB38O636uD0HoNQQ_pe8sGq9Cf_-T-lmxE0okCWfDcloGQ?testcase_id=6684308601569280

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.

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

ClusterFuzz testcase 6565168716972032 is flaky and no longer reproduces, so closing issue.

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