Predator could not provide any possible suspects.
Assigning to concern owner from CL --
https://chromium.googlesource.com/chromium/src/+log/90388a48697cce7562029069c48312e9399a4f63..0e8f3adfdaca42403bf90dda5baabe70ca1fbc3a?pretty=fuller&n=10000

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/0d4eb8a5f8d99d365459af21442cbc7b8648cf66

@rockot -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

ClusterFuzz has detected this issue as fixed in range 502608:502648.

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

Fuzzer: jsbell_serviceworker
Job Type: windows_asan_chrome
Platform Id: windows

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: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=501818:501860
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=502608:502648

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

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.