New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 834555 link

Starred by 1 user
Status: Assigned
Owner:
wolenetz@chromium.org
Cc:
█ brajkumar@chromium.org
wolenetz@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Timeout in mediasource_ADTS_pipeline_integration_fuzzer

Project Member Reported by ClusterFuzz, Apr 19 2018 
Detailed report: https://clusterfuzz.com/testcase?key=6510659957948416

Fuzzer: libFuzzer_mediasource_ADTS_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=505170:505228

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

Issue filed automatically.

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

Comment 1 by brajkumar@chromium.org, Apr 24 2018

Cc: brajkumar@chromium.org
Components: Internals>Media>Source
Labels: -Pri-1 M-66 Test-Predator-Wrong Pri-2
Owner: wolenetz@chromium.org
Status: Assigned (was: Untriaged)
Predator could not provide any possible suspects.

From the above CL observing some changes related to 'pipeline_integration_fuzzertest.cc' , hence suspecting the same

Suspect CL: https://chromium.googlesource.com/chromium/src/+/b61fbbdfbb07406e7e293771f09aace9494bf582

wolenetz@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!
Project Member

Comment 2 by ClusterFuzz, Jun 13 2018

Labels: OS-Mac
Project Member

Comment 3 by ClusterFuzz, Oct 11

Labels: OS-Windows
Project Member

Comment 4 by ClusterFuzz, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6510659957948416 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.

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

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

Comment 7 by ClusterFuzz, Dec 12

Labels: OS-Chrome
►

Sign in to add a comment