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

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

Umm it's hard to tell what's wrong with this.

ClusterFuzz has detected this issue as fixed in range 559240:559263.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  BindRepeating<
  BindRepeating<
  blink::LocalFrameView::SetupRenderThrottling
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=548271:548273
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=559240:559263

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

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 5845410900606976 is verified as fixed, so closing issue as verified.

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