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

Issue 740466 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Out-of-memory in libxml_xml_read_memory_fuzzer

Project Member Reported by ClusterFuzz, Jul 10 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=6613357301071872

Fuzzer: libFuzzer_libxml_xml_read_memory_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  libxml_xml_read_memory_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=395675:395769

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


Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 
Cc: msrchandra@chromium.org
Labels: Test-Predator-Wrong-CLs M-61
Owner: mmoroz@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL did not provide any possible suspects.
Using Code Search for the file, "libxml_xml_read_memory_fuzzer" assigning to concern owner.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/d61bcad3017676cfbc1a53c65a51ffcef331b56e

@mmoroz -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by mmoroz@chromium.org, Jul 10 2017

Components: Blink>XML
Owner: dominicc@chromium.org
Looks like a valid OOM crash.
Project Member

Comment 3 by ClusterFuzz, Aug 9 2017

Status: WontFix (was: Assigned)
ClusterFuzz testcase 6613357301071872 is flaky and no longer reproduces, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Sign in to add a comment