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 761686  with label reproducible, hence assigning to the same dev for more updates.

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

Thanks!

ClusterFuzz has detected this issue as fixed in range 557410:557412.

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

Fuzzer: libFuzzer_renderer_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  renderer_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=455790:455825
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=557410:557412

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 4850496838565888 is verified as fixed, so closing issue as verified.

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