CHECK failure: false in aligned_memory.cc |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5434940058238976 Fuzzer: j00ru_htmlcss_fuzz Job Type: linux_asan_chrome_v8_arm Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: false in aligned_memory.cc base::AlignedAlloc cc::ListContainerHelper::CharAllocator::AllocateNewList Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=557063:557066 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5434940058238976 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
May 14 2018
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
May 15 2018
This issue looks similar to bug 834627 , hence assigning to the same owner for more updates on it. wjmaclean@ Could you please take a look in to this issue? Thanks!
,
May 15 2018
ClusterFuzz has detected this issue as fixed in range 558586:558587. Detailed report: https://clusterfuzz.com/testcase?key=5434940058238976 Fuzzer: j00ru_htmlcss_fuzz Job Type: linux_asan_chrome_v8_arm Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: false in aligned_memory.cc base::AlignedAlloc cc::ListContainerHelper::CharAllocator::AllocateNewList Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=557063:557066 Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=558586:558587 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5434940058238976 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
May 15 2018
ClusterFuzz testcase 5434940058238976 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, May 14 2018