PTAL. I though these error position differences should have gone away after the switch?

CC ross as bisect points to:
https://chromium-review.googlesource.com/c/568484/

This is an invalid asm.js module. Hence falls back to the TurboFan-without-deopt pipeline for now. This will go away after we removed full-codegen. Will keep this on my plate and verify in ~2 weeks. Thanks!

ClusterFuzz has detected this issue as fixed in range 47276:47277.

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

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_turbo
  sources: c4f
  
Sanitizer: address (ASAN)

Regressed: V8: 46647:46648
Fixed: V8: 47276:47277

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

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.

The above comment #4 is correct. This is fixed.

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

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