Crash in blink::reportOOMErrorInMainThread |
|||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=6397740030623744 Fuzzer: libfuzzer_v8_serialized_script_value_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: UNKNOWN Crash Address: 0x00000b0ab65e Crash State: blink::reportOOMErrorInMainThread v8::Utils::ReportOOMFailure v8::internal::V8::FatalProcessOutOfMemory Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=424424:424496 Minimized Testcase (0.72 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97Sdq392GEH-C34L-1BaUbIcVsf6l9kE8KDshVSDaQQO4WCjqR16hHoo0RE17zn4y9QcFFHirmPl2KHgDC_HDQsOQqoOSfO7vQ-D0Wciuall5k3Yxno_QaRfyRLR47Sb-pZMm3xIyDZKIcIXDNhGmak2UdbTw?testcase_id=6397740030623744 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Oct 21 2016
This also blocks fuzzer from finding any good bugs, see https://bugs.chromium.org/p/chromium/issues/detail?id=654868#c16 which fails on corpus merging as well.
,
Oct 21 2016
this is an oom in V8. following guidance in https://github.com/v8/v8/wiki/Triaging-issues and setting labels.
,
Oct 23 2016
,
Oct 24 2016
It is an OOM which on itself is not a "bad" crash. CC'ing CF sheriff for further analysis.
,
Oct 25 2016
This only happened once, now working fine, and fixes in crbug.com/658578 should make this even harder.
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by mmohammad@chromium.org
, Oct 19 2016Status: Assigned (was: Untriaged)