Issue metadata
Sign in to add a comment
|
Direct-leak in AllocateAndInitializeSlotSet |
||||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4858603113807872 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=4858603113807872 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Jul 18 2017
,
Aug 21 2017
Ulan, PTAL
,
Aug 23 2017
,
Aug 24 2017
The NextAction date has arrived: 2017-08-24
,
Aug 24 2017
Looks very similar to issue 728616 which happened in a similar time frame. Also, looking at the stack traces on the fuzzer I see tons of other leaks. It looks like the same issue?
,
Aug 24 2017
This looks identical to 728616 to me. Suggest duping on it.
,
Aug 24 2017
Yeah, looks like the same issue, thanks! As it happens again and again, we probably need to find some solution, e.g. disable leaks detection for AFL as suggested in https://bugs.chromium.org/p/chromium/issues/detail?id=728616#c8
,
Aug 24 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ClusterFuzz
, Jul 9 2017