CHECK failure: size <= kMaxRegularHeapObjectSize in runtime-internal.cc |
||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5630598868893696 Fuzzer: inferno_layout_test_unmodified Job Type: windows_asan_content_shell Platform Id: windows Crash Type: CHECK failure Crash Address: Crash State: size <= kMaxRegularHeapObjectSize in runtime-internal.cc gin::PrintStackTrace v8::internal::Runtime_AllocateInNewSpace Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=507253:507276 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5630598868893696 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Oct 10 2017
ClusterFuzz has detected this issue as fixed in range 507362:507375. Detailed report: https://clusterfuzz.com/testcase?key=5630598868893696 Fuzzer: inferno_layout_test_unmodified Job Type: windows_asan_content_shell Platform Id: windows Crash Type: CHECK failure Crash Address: Crash State: size <= kMaxRegularHeapObjectSize in runtime-internal.cc gin::PrintStackTrace v8::internal::Runtime_AllocateInNewSpace Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=507253:507276 Fixed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=507362:507375 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5630598868893696 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.
,
Oct 10 2017
ClusterFuzz testcase 5630598868893696 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 pnangunoori@chromium.org
, Oct 9 2017Labels: Test-Predator-Wrong M-63