clemensh, can you take a look at this please?

Might be related to  Issue 782277 

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

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

ClusterFuzz has detected this issue as fixed in range 514517:514547.

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

Fuzzer: libFuzzer_v8_wasm_compile_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  slot == stack_state.end() in liftoff-assembler.cc
  v8::internal::wasm::LiftoffAssembler::CacheState::InitMerge
  Br
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514360:514382
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514517:514547

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

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

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

This was fixed in https://chromium-review.googlesource.com/c/v8/v8/+/756705.

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

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