This goes back to this revert:
https://chromium.googlesource.com/v8/v8/+log/f3dcdf886213b9bb36fe40fbde85d4fca6587fb7..89b7a4d7d0a2539c8e3d2422f90c6f6fbdecd0a6?pretty=fuller

PTAL

The symptoms are just different stack traces. This is a known problem. I assume the CLs that got reverted improved it and the revert now looks like the culprit. Are those CLs going to reland?

 Issue 683337  has been merged into this issue.

 Issue 683473  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 42618:42619.

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

Fuzzer: foozzie_js_mutation
Job Type: foozzie_ignition_staging
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,fullcode:x64,ignition_staging
  sources: 019
  
Sanitizer: address (ASAN)

Regressed: V8: 42483:42484
Fixed: V8: 42618:42619

Minimized Testcase (1.01 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95QxJKEURcEkjGbzkCoL7GTiEHeZoVenoNY8IMZFMD42u0TCZgc4x2FbeZhKa_tZham5IXE_8JZvfRkx7B6QhNjLJvuCHDSMulvxCu67uaS04YtGN9wqdKSEC4ZpN_tR85i6czrlFb6V0Nvh8wpMW_WeFzupB5WkHMbhgIVzc4ouplhKQJXo1_msrPbSEG-Q_Lg2KIcaKNsonw8OgnYHr7c6iQslPJnjLvyTxt8VvYSBZvn-ZZb4Nji-wg1NNEukn9ATa4G8Z2MUN0nU7-XAU1UfkgoVbuFzSj5Yr4fDotv4gzbJlhIifdVpuFY_gi0jQZ6LFqml7B7hATjhMRDhpecuq39xdWtjezCqJ-i1vb-j8A-a_g?testcase_id=5929575684243456

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.

ClusterFuzz testcase 5772886150479872 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

adding bmeurer@, who would be better equipped to answer #2.

For now the decision is to not reland the CLs, but wait for I+TF to ship.