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

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

Thanks for reporting this. It looks like we might be attempting to create a mipmap from a 0x0 sized image. It's most probably benign, but I'll have a look at how to avoid that.

ClusterFuzz has detected this issue as fixed in range 502391:502452.

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

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=478736:478797
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=502391:502452

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

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

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