New issue
Advanced search Search tips

Issue 906472 link

Starred by 2 users
Status: Assigned
Owner:
dalecur...@chromium.org
Cc:
kkaluri@chromium.org
dalecur...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Timeout in mediasource_WEBM_OPUS_VP9_pipeline_integration_fuzzer

Project Member Reported by ClusterFuzz, Nov 19 
Detailed report: https://clusterfuzz.com/testcase?key=5051052989349888

Fuzzer: libFuzzer_mediasource_WEBM_OPUS_VP9_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  mediasource_WEBM_OPUS_VP9_pipeline_integration_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=583292:583305

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5051052989349888

Issue filed automatically.

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

Comment 1 by kkaluri@chromium.org, Nov 19

Cc: kkaluri@chromium.org
Labels: M-71 Test-Predator-Wrong CF-NeedsTriage
Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from dev team to look in to this issue.

Thanks!

Comment 2 by manoranjanr@google.com, Nov 19

Cc: dalecur...@chromium.org
Components: Internals>Media
Labels: -CF-NeedsTriage
dalecurtis@, just wondering do you have any inputs here?

Thank you!

Comment 3 by dalecur...@chromium.org, Nov 19

Labels: -Pri-1 Pri-3
Owner: dalecur...@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 4 by ClusterFuzz, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 5051052989349888 appears to be flaky, updating reproducibility label.

Comment 5 by infe...@chromium.org, Dec 1

Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
►

Sign in to add a comment