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

Issue 815405 link

Starred by 1 user
Status: Assigned
Owner:
█ jcivelli@chromium.org
Last visit > 30 days ago
Cc:
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Out-of-memory in xml_parser_fuzzer

Project Member Reported by ClusterFuzz, Feb 24 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5984184057987072

Fuzzer: libFuzzer_xml_parser_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  xml_parser_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=520292:520325

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

Issue filed automatically.

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

Comment 1 by brajkumar@chromium.org, Feb 26 2018

Cc: brajkumar@chromium.org
Components: Blink>XML
Labels: -Pri-1 -Type-Bug M-65 Test-Predator-Wrong Pri-2 Type-Bug-Regression
Owner: jcivelli@chromium.org
Status: Assigned (was: Untriaged)
Predator could not provide any possible suspects.

From the below CL observing some changes related to 'xml_parser_fuzzer' hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/d732ab1c1ee55b334cb284cb1f2cd5ee96e59b79..525ebafbc5297af32a97ab9d4739d7119e274029?pretty=fuller&n=10000

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

jcivelli@ -- 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, Apr 18 2018

Labels: OS-Mac
Project Member

Comment 3 by ClusterFuzz, Oct 9

Labels: OS-Windows
Project Member

Comment 4 by ClusterFuzz, Dec 1

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

Sign in to add a comment