Ill in v8::Utils::ReportOOMFailure |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6562255910207488 Fuzzer: libFuzzer_v8_regexp_parser_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Ill Crash Address: 0x7fe511d811a8 Crash State: v8::Utils::ReportOOMFailure v8::internal::V8::FatalProcessOutOfMemory v8::internal::Factory::NewCodeRaw Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=490950:491000 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6562255910207488 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Sep 28 2017
,
Sep 28 2017
This looks like a normal OOM crash, trying to allocate memory for code as part of regexp processing. I'm not sure how much memory was requested and why allocation failed.
,
Oct 1 2017
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
,
Oct 5 2017
I think applying Blink>JavaScript>Runtime is wrong. Blink>JavaScript would be more appropriate. I will kick-off a separate email thread to fix that problem.
,
Oct 5 2017
,
Oct 24 2017
For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md. The link referenced in the description is no longer valid.
,
Nov 7 2017
,
Dec 6 2017
ClusterFuzz testcase 6562255910207488 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by kkaluri@chromium.org
, Sep 20 2017Labels: Test-Predator-Wrong