Using the provided regression range assigning to the possible suspect as per the change made for the file, “gles2_cmd_decoder_passthrough_doers.cc”
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/42c78a82903338fb92e11dd4121a7db81139f578

@geofflang  -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Thanks!

ClusterFuzz has detected this issue as fixed in range 525196:525219.

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

Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x00000000000c
Crash State:
  gpu::gles2::TextureBase::target
  gpu::gles2::GLES2DecoderPassthroughImpl::DoDeleteTextures
  gpu::gles2::GLES2DecoderPassthroughImpl::HandleDeleteTexturesImmediate
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=522790:522815
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=525196:525219

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

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

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