The regression range is really old but it the crash is still in ToT.

ClusterFuzz has detected this issue as fixed in range 36045:36046.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5062117186600960

Fuzzer: decoder_langfuzz
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !feedback_vector_->metadata()->SpecDiffersFrom( literal()->feedback_vector_spec(
  
Regressed: V8: r29964:29965
Fixed: V8: r36045:36046

Minimized Testcase (7.34 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95eK_RVVk_dVl20zs50HiWT2ewAZyNKqkC_PIQ-4QVB1w_Fp2-jgim0ilZJJlVHF4-Vo4Na7vh6ykch0blG_1XHYpVwWsVYHEGcI1JKSkIfa40yJewwgoqsWXF38wViwh4tGFrITXfCgNnGjggRJ1PtzTE5lw

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

This seems to have been fixed by Adam's fix as well. I think we can mark this as fixed. WDYT?

https://chromium.googlesource.com/v8/v8/+/75f2d65f003ebb22815489e9970913ba37234f1b

Yep! Always scoping + sloppy eval is the source of vector mismatch errors. :p

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot