Predator could not provide any possible suspects.
Using the CL search for the file, “ipc_channel_proxy.cc” assigning to concern owner.

Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/8b8c9061a909fdda9125c8d72631a9cf46dc37f8

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


Thank You.

Not sure what component to tag this with.

The issue is that things which log to the JS console also send the logged data over IPC to the browser, and this data may exceed the max allowed IPC size.

Seems https://cs.chromium.org/chromium/src/content/shell/renderer/layout_test/blink_test_runner.cc?type=cs&sq=package:chromium&l=281

can go over the IPC size.

ClusterFuzz has detected this issue as fixed in range 544435:544631.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: CHECK failure
Crash Address: 
Crash State:
  message->size() <= Channel::kMaximumMessageSize in ipc_channel_proxy.cc
  IPC::ChannelProxy::SendInternal
  IPC::SyncChannel::Send
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=502634:502656
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=544435:544631

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

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.