Yet another one strange crash by v8_wasm :)

ahaas@, please feel free to re-assign if needed. I'm assigning these crashes to you as an author of the fuzzers. Hope that you don't regret about writing them :)

ClusterFuzz has detected this issue as fixed in range 420584:420606.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5971030491529216

Fuzzer: libfuzzer_v8_wasm_asmjs_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  Disposing the isolate that is entered by a thread in handles.h
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=403610:403611
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=420584:420606

Minimized Testcase (0.19 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95G_HlIGgvvi3rEEGCa5sIh1JhDI9IxPg2yOXhW9GqDRiRZjldMqOoY3d9akZ78OE_Eznbzfh8N6tf4Ylu1JIX7W_n5UWE6X62sB7DUvD1QKI51LnJHcfyLgs39L2KRGUtxo8-Z_eIGXgesdzAt9HK9b4MdCA?testcase_id=5971030491529216

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

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