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

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

Thanks!  Nick, would you have any time to look at this?  I think it's in the old renderer-side code.  (I wonder if we can just remove that now?)

ClusterFuzz has detected this issue as fixed in range 544768:544771.

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

Fuzzer: inferno_twister
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  content::SiteIsolationStatsGatherer::OnReceivedResponse
  content::ResourceDispatcher::OnReceivedResponse
  content::URLLoaderClientImpl::OnReceiveResponse
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=523898:523900
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=544768:544771

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

Additional requirements: Requires HTTP

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

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