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 suspected CL's 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 563899:563909.

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

Fuzzer: j00ru_htmlcss_fuzz
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000040
Crash State:
  __msan_memset
  blink::TimerBase::Stop
  blink::IdlenessDetector::Shutdown
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=399234:399406
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=563899:563909

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

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

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