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, “ozone_platform.cc” assigning to concern owner.

Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/faa974734a75c2fc4b855f2b67afda7f2aa4efe0

sadrul@ -- Assigning this issue to you as are the reviewer and we are unable to assign it to akariasai@, kindly reassign if it has nothing to do with the above changes.


Thank You.

ClusterFuzz has detected this issue as fixed in range 525358:525384.

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

Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  instance_. OzonePlatform is not initialized in ozone_platform.cc
  ui::OzonePlatform::GetInstance
  gl::init::GetSurfaceFactoryOzone
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=525156:525177
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=525358:525384

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 5617158112673792 is verified as fixed, so closing issue as verified.

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