Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/1c5529993dfd0afd3545708a41896456c0d25d70 (Reland "[modules] Implement import.meta proposal").

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

Kouhei -- can you please check if you can repro this?

I don't think this is a modules bug at all. 

https://clusterfuzz.com/v2/testcase-detail/6345116204924928 seems to point to a turbofan bug. 

Removing labels.

Benedikt, can you ptal?

+clemens (v8's clusterfuzz sheriff)

That looks a lot like the Unreachable business, tebbi@ can you check?

ClusterFuzz has detected this issue as fixed in range 508344:508361.

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

Fuzzer: inferno_webbot
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Breakpoint
Crash Address: 0x4a0ae080
Crash State:
  v8::internal::Invoke
  v8::internal::Execution::Call
  v8::Function::Call
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=508188:508235
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=508344:508361

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

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.

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

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