Direct-leak in uprv_malloc_58 |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6508297017622528 Fuzzer: v8_builtins_generator Job Type: linux_asan_d8_v8_arm64_dbg Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: uprv_malloc_58 icu_58::UMemory::operator new icu_58::BreakIterator::buildInstance Sanitizer: address (ASAN) Regressed: V8: 44701:44702 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6508297017622528 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Apr 25 2017
As discussed offline, the regression range for this report goes a little bit further back than the CL that exposed "console" via "d8". Maybe this is helpful.
,
Apr 27 2017
ClusterFuzz has detected this issue as fixed in range 44879:44880. Detailed report: https://clusterfuzz.com/testcase?key=6531640164876288 Fuzzer: v8_builtins_generator Job Type: linux_asan_d8_dbg Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: uprv_malloc_58 icu_58::UMemory::operator new v8::internal::CreateICUDateFormat Sanitizer: address (ASAN) Regressed: V8: 44796:44797 Fixed: V8: 44879:44880 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6531640164876288 See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Apr 27 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Apr 25 2017