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 assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/bb1ff6ae23813a01f053dbc64ccf032b8a4c4025 (Implement bindImageTexture for webgl2-compute).

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.

It's not possible that this regression is caused by my change. There are below reasons:
1. Currently, webgl2-compute context is only enabled for passthrough command decoder. The context creation will fail if it's a validating command decoder(See https://chromium-review.googlesource.com/c/chromium/src/+/1149711). All APIs of webgl2-compute are also only supported for passthrough cmd decoder. But the crash happens in validating command decoder. So it's not possible that my change caused this regression.
2. The crash is a buffer CHECK failure. My code has nothing to do with the buffer.

ClusterFuzz has detected this issue as fixed in range 580086:580090.

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

Fuzzer: afl_gpu_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  buffer_count_ == 0u in buffer_manager.cc
  gpu::gles2::BufferManager::~BufferManager
  gpu::gles2::BufferManager::~BufferManager
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=579277:579284
Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=580086:580090

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

Additional requirements: Requires Gestures

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

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