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

mstarzinger: ptal. Thanks!

There's only one commit in the regression range: https://chromium.googlesource.com/v8/v8/+log/53553f5dcbc725a48965d68b1d4c5671257242d8..65bd1a300ac1a040eb08dcfe25a3d0635392ea34?pretty=fuller

+cc rmcilroy

Regression range points to 65bd1a300ac1a040eb08dcfe25a3d0635392ea34. This could very well be the same root cause as with  issue v8:6589 , for which I have a fix in flight. I will verify after that fix landed.

Yep, I just verified that bf10f659767341fa24140e6996e7e684636e0b0b fixed it.

Thanks Michi!

ClusterFuzz has detected this issue as fixed in range 46693:46694.

Detailed report: https://clusterfuzz.com/testcase?key=6297950572773376

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !v8::internal::FLAG_enable_slow_asserts || (object->IsJSFunction()) in objects-i
  cast
  v8::internal::OptimizedFrame::Summarize
  
Sanitizer: address (ASAN)

Regressed: V8: 46683:46684
Fixed: V8: 46693:46694

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6297950572773376


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.

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