Unable to find actual suspect through code search nor from the provided regression range, hence adding appropriate label for further triage.

Thanks!

Per - could you PTAL?

I've got a local fix. Will upload CL in the next few days.

ClusterFuzz has detected this issue as fixed in range 540793:540796.

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

Fuzzer: libFuzzer_audio_processing_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  0 < AvaliableSpace() in aec_core.cc
  rtc::FatalMessage::~FatalMessage
  webrtc::BlockBuffer::ExtractExtendedBlock
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=537978:537991
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=540793:540796

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

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.

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

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

Regarding #6: I Guess that this cannot be assumed to be fixed, so that mist be wrong.