Through code search on file feature_info.cc, suspected CL is https://chromium.googlesource.com/chromium/src/+/e2f29f0eda0cb38f57db34c7343ef4e6cce40263
reveman@, could you please take a look and reassign if it is not related your changes.

Crash in IsGL_REDSupportedOnFBOs is usually what I see when drivers are in a weird state. Could be related to my change but hard to see how that would happen.

ClusterFuzz has detected this issue as fixed in range 455091:455226.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4874477608632320

Fuzzer: libfuzzer_gpu_angle_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e9000069e9
Crash State:
  base::debug::DebugBreak
  gpu::gles2::IsGL_REDSupportedOnFBOs
  gpu::gles2::FeatureInfo::InitializeFeatures
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=437773:438087
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=455091:455226

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94Atnr9ZqYzbTuZc6No-8ywhLrC6v8yOB4Ju9dXAzVA55PGFU_cqoQS9ThbpCJ3_E835ftdYEGrnQJGFES3q8icNKuwG6XsmB3bk3c8PI0Tf0WUujHqrnzLSHQSfPl8QBJkXFpBBvG4Au6dGPuso10oQZmLrqLmq8FkL1fEIWrJzyNQ1--jX3vci82XPvgUYVr8iicdofCV2S5bikXE88dcyCIri5Ss2V95PnDtfVRcFUPpsr3NqzncALq-9M-0rvAgWkbxm17cn-0xMEGm_sJQVfLAPMeCMTE2NhgNNrkK8j_hQlwGfrOZIPD9sfHthzrY6Z1-Z3UFZ-HcCG70etjr4TWS6gvEHUCkbOAl21klrTZu1f0?testcase_id=4874477608632320


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

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