peah@, this looks to be regression from your recent changes, can you please take a look.

Thanks!
I have a CL ready that fixes that issue.

This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

The issue should now be fixed. Is there any way that I  can verify that the fixing CL has the intended effect?

ClusterFuzz has detected this issue as fixed in range 535958:535961.

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

Fuzzer: libFuzzer_audio_processing_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  webrtc::AecState::Update
  webrtc::EchoRemoverImpl::ProcessCapture
  webrtc::BlockProcessorImpl::ProcessCapture
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=535484:535496
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=535958:535961

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

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 5597659231158272 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