Predator and CL could not provide any possible suspects.
Using Code Search for the file, "Device.cpp" assigning to the concern owner who might be related.

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

Looks like  Issue 764461  with a different stack trace.

Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

ClusterFuzz has detected this issue as fixed in range 509892:509921.

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

Fuzzer: libFuzzer_gpu_swiftshader_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  false
  es2::Device::stretchRect
  es2::Texture2D::generateMipmaps
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=502503:502506
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=509892:509921

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

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

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