Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/7df6feaddfff789abbef65a84c1a4296c5927a0a (Migrate call-sites away from un-managed PlatformHandle[Vector]s.).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Appears to be the CHECK added in https://chromium-review.googlesource.com/666082 firing, i.e. that something tries to send a message that is too-large.

Looks like coincidence that this showed up when it did; I'm able to trivially repro with the Reproducer Testcase, even after reverting the PlatformHandle changes.

ClusterFuzz has detected this issue as fixed in range 547166:547168.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  message->data_num_bytes() < GetConfiguration().max_message_num_bytes in node_cha
  mojo::edk::NodeChannel::WriteChannelMessage
  mojo::edk::NodeChannel::SendChannelMessage
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=518240:518474
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=547166:547168

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

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

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