Predator could not provide any possible suspects.

From the below CL observing some changes related to 'gles2_cmd_decoder.cc' hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/0023f0453fc09e15f31969f498e0039588e799a4..c12349df233fd24786c532115ada069b1f31a4fb?pretty=fuller&n=10000

Suspect CL: https://chromium.googlesource.com/chromium/src/+/fdec674e8373793d4eb226f0e18771bbeeea3792

geofflang@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

This failure is not due to my change.  I'm not familiar with the code around the call stack at all so I wouldn't know how to assign this.

Unable to find actual suspect through code search as well, marking it as untriaged and requesting someone from mojo team to look in to this issue.

Thanks!

ClusterFuzz has detected this issue as fixed in range 541413:541420.

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

Fuzzer: ochang_domfuzzer
Job Type: windows_asan_content_shell
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  outgoing_messages_.size() <= 100000u in channel_win.cc
  mojo::edk::ChannelWin::Write
  mojo::edk::NodeChannel::WriteChannelMessage
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=538472:538495
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=541413:541420

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

Additional requirements: Requires HTTP

See https://github.com/google/clusterfuzz-tools 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 6103590054395904 is verified as fixed, so closing issue as verified.

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