This is hitting an assert that is more of an alert when running with a debug build than an actual should-not-happen. I guess we should discern between those when building as part of Chromium versus when creating a standalone build for debugging.

ClusterFuzz has detected this issue as fixed in range 491548:491642.

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

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=491548:491642

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


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

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