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/+/98d9999686694ff5774549e4a43a1d8c75859a78 (Avoid crashes if all favicons already processed).

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.

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

Suggested patch is about favicons and almost certainly unrelated.

Adjust component label based on stacktrace. 

ClusterFuzz has detected this issue as fixed in range 550043:550047.

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

Fuzzer: mbarbella_js_mutation_layout
Job Type: windows_asan_content_shell
Platform Id: windows

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x118deea442a0
Crash State:
  [thunk]:rtc::VideoSourceInterface<class
  base::internal::Invoker<struct base::internal::BindState<void
  base::PostTaskAndReplyRelay::RunTaskAndPostReply
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=549052:549053
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=550043:550047

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

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