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/+/b4e6da646f25cca291318e50e7aa9dd05173dd65 (chromeos: makes ScreenProviderObserver an associated interface).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

The offending patch was reverted. I relanded the patch after fixing the null read.

ClusterFuzz has detected this issue as fixed in range 575962:575964.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  ash::WindowTreeHostManager::OnDisplayMetricsChanged
  display::DisplayManager::NotifyMetricsChanged
  display::DisplayManager::UpdateDisplayBounds
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_chromeos&range=575794:575806
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_chromeos&range=575962:575964

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

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

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