Abrt in media::Ranges<base::TimeDelta>::DCheckLT |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5135869127426048 Fuzzer: libFuzzer_mediasource_MP4_AACSBR_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Abrt Crash Address: 0x03e900004d4b Crash State: media::Ranges<base::TimeDelta>::DCheckLT media::Ranges<base::TimeDelta>::Add media::ChunkDemuxerStream::GetBufferedRanges Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5135869127426048 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
,
Mar 26 2018
,
Mar 26 2018
This looks like it might be a duplicate (w/different fuzzer) of P2 bug 763620. I'll repro it locally to confirm that assumption.
,
Mar 26 2018
Weird - the repro case instead hits timeout pending CDM being setup (known bug 761023 ). I was unable to repro the DCHECK failure with the repro testcase linked in the OP. mmoroz@ : the report seems excessively long. Is the fuzzer infra perhaps reporting the wrong case for this issue?
,
Mar 26 2018
Ah - I just noticed the bold disclaimer in OP: Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days. I'll close this issue, since it's either a duplicate of one or more of: bug 763620 bug 761023
,
Mar 26 2018
Matt, thanks for the heads up. For some reason, the stacktrace contains logs of merge process that happens when fuzzing is finished. That should not be there, I've filed a bug for CF: issue 825914.
,
Mar 30 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ClusterFuzz
, Mar 26 2018Labels: Test-Predator-Auto-Components