Predator and CL did not provide any possible suspects.
Using Code Search for the file, "feature_info.cc" assigning to the concern owner from GIT Blame.

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

@zmo -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

ClusterFuzz has detected this issue as fixed in range 500153:500205.

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

Fuzzer: libFuzzer_gpu_angle_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  glGetError() == GL_NO_ERROR in feature_info.cc
  base::debug::DebugBreak
  gpu::gles2::IsGL_REDSupportedOnFBOs
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=469306:469316
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=500153:500205

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

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

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