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

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/45a0c949c2a456761ffa3011f7058c3d8b7a2d96 (Implement tail processing for AudioNodes).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

ClusterFuzz has detected this issue as fixed in range 547460:547462.

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

Fuzzer: attekett_webaudio_fuzzer
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x122a8216d298
Crash State:
  blink::DeferredTaskHandler::FinishTailProcessing
  blink::OfflineAudioContext::FireCompletionEvent
  blink::RunCrossThreadClosure
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=543865:543928
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=547460:547462

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

See https://github.com/google/clusterfuzz-tools 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 6151373478166528 is verified as fixed, so closing issue as verified.

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

Also found by internal fuzzers, I'm afraid.

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