Direct-leak in AllocateAndInitializeSlotSet |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6392246999187456 Fuzzer: afl_v8_serialized_script_value_fuzzer Job Type: afl_chrome_asan Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: AllocateAndInitializeSlotSet v8::internal::SlotSet* v8::internal::MemoryChunk::AllocateSlotSet< Insert<v8::internal::AccessMode::ATOMIC> Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=480804:480889 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6392246999187456 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Aug 28 2017
Not actionable. Leak due to unclean fuzzer shutdown.
,
Sep 4 2017
ClusterFuzz testcase 6392246999187456 is still reproducing on tip-of-tree build (trunk). If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase. Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace. |
|||
►
Sign in to add a comment |
|||
Comment 1 by msrchandra@chromium.org
, Aug 28 2017Labels: M-61 Test-Predator-Wrong