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 adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/13676929c2a6917d70e22ce3cf56ed3be605795c (Improve system_healtm.memory_mobile metrics).

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.

ClusterFuzz has detected this issue as fixed in range 618402:618408.

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

Fuzzer: libFuzzer_gpu_raster_fuzzer
Fuzz target binary: gpu_raster_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  context_type == context_type_ in feature_info.cc
  gpu::gles2::FeatureInfo::Initialize
  gpu::gles2::ContextGroup::Initialize
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=618245:618246
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=618402:618408

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5413812934803456 is verified as fixed, so closing issue as verified.

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