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

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/7c7176234e553c35a2d8ec014f2caa29f7278065 (Rewrite component update service in terms of components/update_client.).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

It is possible the issue is in the  LoginScreenController based on the stack trace linked by https://clusterfuzz.com/testcase?key=4881153508245504 in the OP.

ClusterFuzz has detected this issue as fixed in range 521102:521135.

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

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=331388:331413
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_chromeos&range=521102:521135

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

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

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