Predator and CL did not find any possible suspects.
Using code search for the file, "media::FFmpegDemuxerStream::EnqueuePacket" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/560640b659f688387d4c239e00f2dc941607e9f0

@dalecurtis -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Thanks, will take a look. 

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

commit 25d15671d9766d5f3cb87b7f5ff810cca5b130e9
Author: dalecurtis <dalecurtis@chromium.org>
Date: Fri Feb 17 01:59:10 2017

Issue a parse error on unexpected negative timestamps.

We should not pass such buffers outside of FFmpegDemuxer.

BUG= 686482 
TEST=new unittest.

Review-Url: https://codereview.chromium.org/2699563002
Cr-Commit-Position: refs/heads/master@{#451172}

[modify] https://crrev.com/25d15671d9766d5f3cb87b7f5ff810cca5b130e9/media/filters/ffmpeg_demuxer.cc
[modify] https://crrev.com/25d15671d9766d5f3cb87b7f5ff810cca5b130e9/media/filters/ffmpeg_demuxer_unittest.cc
[add] https://crrev.com/25d15671d9766d5f3cb87b7f5ff810cca5b130e9/media/test/data/negative_ts.flac

ClusterFuzz has detected this issue as fixed in range 451140:451188.

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

Fuzzer: libfuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e90000791a
Crash State:
  base::debug::DebugBreak
  media::FFmpegDemuxerStream::EnqueuePacket
  media::FFmpegDemuxer::OnReadFrameDone
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=413124:413277
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=451140:451188

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97Dp36p6KPc-29vKOWzfZbM8K729IMl2ENwuC7KVM0d0TMN042-UVBNsQ6zG1x7BflxyN0xY9V2sx5kgLR-IL6TOH_64yXUVBcmhkvjD--YU3krUIcZXC8xhYo6cfaoKT99dxh_yDgMhtVglZq48RCoVAa1Fa9UfCTiOiMvLqkVAZv_N9B36A9-tBA3bLNCGoTK1HQOAUdAwxnK3Fb3N0NcHqjqH0OVnjLF77Zv1EZvKtqdC6dZg-VFOSJIMhGUTidJY1F_qJHRcTcYWn_soe_-OjAqD_fRbEk4a9du5QgkfJ8MyNJhI8EWoTeKROd6MSLlLw8J0bwN5r29De5W6ooAAS67pZ8mGQbyVwaPYPw268J7Uyo?testcase_id=6577998171209728


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 6577998171209728 is verified as fixed, so closing issue.

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