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

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

Unable to find actual suspect through code search and also observing no CL under regression range, hence adding appropriate label and requesting someone from blink team to look in to this issue.

Thanks!

ClusterFuzz has detected this issue as fixed in range 559242:559282.

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

Fuzzer: marty_html_twiddler
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  base::PostTaskAndReplyRelay::RunReply
  base::internal::Invoker<base::internal::BindState<void
  base::debug::TaskAnnotator::RunTask
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=559242:559282

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

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

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