Issue metadata
Sign in to add a comment
|
Bad-cast to std::__1::__shared_weak_count from invalid vptr;v8::internal::wasm::AsyncCompile;v8::WebAssemblyCompile |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5063042462384128 Fuzzer: ochang_js_fuzzer Job Type: linux_ubsan_vptr_d8 Platform Id: linux Crash Type: Bad-cast Crash Address: 0x7f7b5ec209a0 Crash State: Bad-cast to std::__1::__shared_weak_count from invalid vptr v8::internal::wasm::AsyncCompile v8::WebAssemblyCompile Sanitizer: undefined (UBSAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=48976:48977 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5063042462384128 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Oct 31 2017
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Oct 31 2017
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/1b2a341e0223a3e09c7366f3eb5d24fc8da29a8e ([snapshot] Move bytecode handlers to builtins snapshot). If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
,
Nov 2 2017
Looks unrelated to (de)serialization of interpreter bytecode handlers. +titzer fyi.
,
Nov 2 2017
Assigning to ahaas, as it looks to be either an async compile or streaming compile issue.
,
Nov 7 2017
,
Nov 7 2017
,
Nov 9 2017
ClusterFuzz has detected this issue as fixed in range 49219:49220. Detailed report: https://clusterfuzz.com/testcase?key=5063042462384128 Fuzzer: ochang_js_fuzzer Job Type: linux_ubsan_vptr_d8 Platform Id: linux Crash Type: Bad-cast Crash Address: 0x7f7b5ec209a0 Crash State: Bad-cast to std::__1::__shared_weak_count from invalid vptr v8::internal::wasm::AsyncCompile v8::WebAssemblyCompile Sanitizer: undefined (UBSAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=48976:48977 Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=49219:49220 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5063042462384128 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.
,
Nov 9 2017
,
Nov 9 2017
This issue happens in a feature which is turned off by default at the moment. That's why I removed the Security_Severity-High label.
,
Nov 9 2017
ClusterFuzz testcase 5063042462384128 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Nov 9 2017
,
Feb 15 2018
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sheriffbot@chromium.org
, Oct 28 2017