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

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

This issue looks similar to  bug 822618 , hence cc'ing to the same dev on same for more updates on this issue.

jbroman@ Could you please take a look in to this issue?

Thanks!

ClusterFuzz has detected this issue as fixed in range 589563:589567.

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

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

Crash Type: Direct-leak
Crash Address: 
Crash State:
  Create
  blink::ModulesInitializer::InstallSupplements
  blink::LocalDOMWindow::InstallNewDocument
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=527088:527090
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=589563:589567

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

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

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