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

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

Predator and CL could not provide any possible suspects.
Using the code search for the file, “message_loop.cc” assigning to concern owner from GIT blame.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/97621d9c31b719379ccdabb8220cca66aad58b8e

@robliao -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

ClusterFuzz has detected this issue as fixed in range 514212:514242.

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

Fuzzer: inferno_webbot
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000008
Crash State:
  base::MessageLoop::RunTask
  base::MessageLoop::DoWork
  base::MessagePumpLibevent::Run
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_chromeos&range=513982:514022
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_chromeos&range=514212:514242

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

Additional requirements: Requires Gestures

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

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

I think there's something wrong with this test or symbolizer. These things shouldn't fix themselves on their own.