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

Issue 833092 link

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



Sign in to add a comment

Timeout in expat_xml_parse_fuzzer

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

Fuzzer: libFuzzer_expat_xml_parse_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=507208:507237

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

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 16 2018

Cc: brajkumar@chromium.org
Components: Blink>XML
Labels: -Pri-1 -Type-Bug M-66 Test-Predator-Wrong CF-NeedsTriage Pri-2 Type-Bug-Regression
Unable to find actual suspect through code search and also observing no suspecting CL under regression range, hence adding appropriate label and requesting someone from blink team to look in to this issue.

Thanks!
Project Member

Comment 2 by ClusterFuzz, Apr 21 2018

Labels: OS-Mac

Comment 3 by schenney@chromium.org, Jul 25

Status: Available (was: Untriaged)
Project Member

Comment 4 by ClusterFuzz, Oct 23

Labels: OS-Windows
Project Member

Comment 5 by ClusterFuzz, Dec 1

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

Comment 6 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 7 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 8 by ClusterFuzz, Dec 9

Labels: OS-Chrome
►

Sign in to add a comment