New issue
Advanced search Search tips

Issue 827481 link

Starred by 1 user
Status: WontFix
Owner:
wolenetz@chromium.org
Closed: Mar 2018
Cc:
mmoroz@chromium.org
wolenetz@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Abrt in media::Ranges<base::TimeDelta>::DCheckLT

Project Member Reported by ClusterFuzz, Mar 30 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5854134184706048

Fuzzer: libFuzzer_mediasource_MP4_AACSBR_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x0539000036c3
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=5854134184706048

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.
Project Member

Comment 1 by ClusterFuzz, Mar 30 2018

Components: Internals>Media
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Comment 2 by dalecur...@chromium.org, Mar 30 2018

Owner: wolenetz@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by wolenetz@chromium.org, Mar 30 2018

Cc: mmoroz@chromium.org
Status: WontFix (was: Assigned)
Repro case is just 1 byte long. No repro.
However, this looks like recent  bug 825770  in that there are tons of lines in the report, with a non-reproducible result.

The DCHECK failure, however, looks like it's a duplicate (from a different fuzzer) of bug 763620.

+mmoroz@ - this looks like it might be another instance of spammy report contents (CF issue 825914)

WontFix'ing per unreproducible with the supplied case, and likely root cause of real failure is already tracked by bug 763620.

Comment 4 by wolenetz@chromium.org, Mar 30 2018

Components: -Internals>Media Internals>Media>Source

Comment 5 by mmoroz@chromium.org, Mar 30 2018 

Ack. I think we have those redundant logs in the stacktrace for every unreproducible crash reported by an in-process fuzz target.
►

Sign in to add a comment