oh wait this is wasm? clemensh@ can you take a look?

Seems related to our current async compilation problems. According to the reported stack trace, Shell::RunMain already finishes when a function callback is called, maybe to resolve the wasm compilation promise.

If we can confirm it is duplicate of v8:6436, let's close it that way.

ClusterFuzz has detected this issue as fixed in range 475250:475393.

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

Fuzzer: inferno_js_fuzzer
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: Heap-use-after-free READ 4
Crash Address: 0x0ba08314
Crash State:
  v8::Shell::CreateRealm
  v8::Shell::RealmCreate
  v8::internal::FunctionCallbackArguments::Call
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=475250:475393

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


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

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This bug requires manual review: M62 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), bhthompson@(ChromeOS), abdulsyed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Already in M61 stable - no idea what Sheriffbot is doing requesting and M62 merge :-)