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/+/56fe24372cbba2a6ef8a2934e6410eb432d8c92f ([wasm][streaming] Do not reject promise upon abort without reason).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

I don't think this issue is caused by my CL.

ClusterFuzz has detected this issue as fixed in range 531401:531402.

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

Fuzzer: mbarbella_js_mutation_layout
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Ill
Crash Address: 0x00000b7e69c3
Crash State:
  v8::internal::Module::RunInitializationCode
  v8::internal::Module::FinishInstantiate
  v8::internal::Module::Instantiate
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=530865:530867
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=531401:531402

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

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 5851449618857984 is verified as fixed, so closing issue as verified.

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