DCHECK failure in (lazy_callee) != nullptr in module-compiler.cc |
||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4800393459793920 Fuzzer: ochang_js_fuzzer Job Type: linux_asan_d8_v8_arm_dbg Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: (lazy_callee) != nullptr in module-compiler.cc V8_Dcheck v8::internal::wasm::LazyCompilationOrchestrator::CompileLazyOnGCHeap Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_v8_arm_dbg&range=49708:49709 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4800393459793920 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Dec 2 2017
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/efed6ba94a722c919d23241117fc4a44f2d06d8a ([wasm] Lazy-compilation: Fix patching of wasm-to-wasm wrappers). If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
,
Dec 2 2017
,
Dec 3 2017
,
Dec 4 2017
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it. If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 7 2017
,
Dec 8 2017
ClusterFuzz has detected this issue as fixed in range 49947:49948. Detailed report: https://clusterfuzz.com/testcase?key=4800393459793920 Fuzzer: ochang_js_fuzzer Job Type: linux_asan_d8_v8_arm_dbg Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: (lazy_callee) != nullptr in module-compiler.cc V8_Dcheck v8::internal::wasm::LazyCompilationOrchestrator::CompileLazyOnGCHeap Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_v8_arm_dbg&range=49708:49709 Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_v8_arm_dbg&range=49947:49948 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4800393459793920 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.
,
Dec 8 2017
ClusterFuzz testcase 4800393459793920 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Dec 8 2017
,
Dec 15 2017
,
Dec 15 2017
This bug requires manual review: M64 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: cmasso@(Android), cmasso@(iOS), kbleicher@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 15 2017
We have too much automation here... Nothing to merge. Also, this was never a security issue, since it requires the '--wasm-lazy-compilation' flag.
,
Mar 16 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 ClusterFuzz
, Dec 2 2017Labels: Test-Predator-Auto-Components