Is this different to the usual false positives? Goes back until:
https://chromium.googlesource.com/v8/v8/+/36d703778ccd0d2777e0d4b69ed6e65e39a9f521

Lower prio, since the diff seems to affect an error message only...

This is the same as https://bugs.chromium.org/p/chromium/issues/detail?id=764152 , just that the FLAG_ commit makes the code more lazy, so this is discovered.

ClusterFuzz has detected this issue as fixed in range 48202:48203.

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:x64,ignition_eager
  sources: b65
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=47802:47803
Fixed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=48202:48203

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

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.