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 adding ccs based on suspected regression changelists:

Make r16_ext textures work with validating decoder. by hubbe@google.com - https://chromium.googlesource.com/chromium/src/+/37924baf9ac8f3ce7811508bc650efe965bb50b2

Revert "Logging to ensure that non-offscreen surfaces are destroyed as expected" by ericrk@chromium.org - https://chromium.googlesource.com/chromium/src/+/7b9fe37fc214c456257f79ff6e9c76d37657100d

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

ClusterFuzz has detected this issue as fixed in range 559059:559067.

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

Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  *length < bufsize in gles2_cmd_decoder_passthrough.h
  gpu::error::Error gpu::gles2::GLES2DecoderPassthroughImpl::GetNumericHelper<long
  gpu::gles2::GLES2DecoderPassthroughImpl::DoGetInteger64v
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=523270:523295
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=559059:559067

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

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

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

https://chromium.googlesource.com/chromium/src/+/a210e801d2389b72e762a446be8651700a71b330 (in the progression range) landed which changes the interpretation of the "config" bits, causing the repro cases to not apply any more (we temporarily lost coverage). CF would eventually restore coverage, but in the mean time let's reopen.