Assuming this as v8 Crash, keeping the status as Available and looping v8 sheriffs. Could some one please look into the issue and update.
Thank You.

ClusterFuzz has detected this issue as fixed in range 414963:414964.

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

Fuzzer: libfuzzer_v8_wasm_asmjs_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x00000054e008
Crash State:
  v8::base::OS::Abort
  V8_Fatal
  v8::internal::SnapshotData::SnapshotData
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=414962:414963
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=414963:414964

Minimized Testcase (0.00 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96kxEcUZk-ip4nQyTPEjBghH_wXch-FQ2SLtwhfU1TDm5DLCs83Be2BvKfXrD_Xx7ejloM73nprMRJ4xbDg0ZEPQ6iH6pTnMebc1eVaX445VwjpTCeLeoKo2oCjVNkaF8D90jraVx5Jy6kLaGYtQiWhH-Xp1g?testcase_id=5001020319203328

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.

ClusterFuzz testcase is verified as fixed, closing issue.

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

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