Through code search on file ffmpeg_demuxer.cc, suspected CL
https://chromium.googlesource.com/chromium/src/+/86a0024f06be519a8dc10ce7d2fc6eea5971645f
dalecurtis@, could you please take a look?

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

commit ebc9c38753d2c3736fa96018bea462c64d1e6602
Author: dalecurtis <dalecurtis@chromium.org>
Date: Tue Apr 04 05:03:09 2017

Ignore start time values matching kNoTimestamp.

ClusterFuzz seems to have honed in on providing a timestamp equal
to std::numeric_limits<int64_t>::min(), which we use as a sentinal
value meaning kNoTimestamp. These should be ignored, similarly to
how we ignore AV_NOPTS_VALUE values when estimating start times.

BUG= 700501 
TEST=clusterfuzz test case passes.

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

[modify] https://crrev.com/ebc9c38753d2c3736fa96018bea462c64d1e6602/media/filters/ffmpeg_demuxer.cc

ClusterFuzz has detected this issue as fixed in range 461622:461634.

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

Fuzzer: libfuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  start_time_estimate != kNoTimestamp in ffmpeg_demuxer.cc
  media::ExtractStartTime
  media::FFmpegDemuxer::OnFindStreamInfoDone
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=455091:455226
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=461622:461634

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv97Y1BFiECWSqWioVME5Cy9kUOIpwmFi5bEeoICxUB6N6lDknpJzXMWEKjmF5dYE3cpciUc7LVvCh_pc6a3QH8yR5pxEsWiachfb7fL1wcdGGbKYkA0J94X0Tvdv2F_askfRzkTmiVeP4-Yhk3gIoosBGxQCQPLbJA3gPqbf8yLvSwbaGHyvXuzAw1HHr4LOmOV3nC4p0SAm31i-4EHbL68pSxETvMJgX8PR00KJnRFCytymU-IfZ2wUl3PZFtUSES3Q650HOCdXH9fd5iDNJ5gf5vAtn2qEplnjbW_5O-tXdTwYEEr170G6hxrOjM1TRpQZjqyY9BcpK02L94QmuZRyV70Q0sNaYydPJJzbOj-oe9kWYAykNthlLCFZZ4cfP31zMXdDOHVNosvnOEnF-4z65qCYng?testcase_id=6751567807250432


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

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