New issue
Advanced search Search tips

Issue 906010 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Nov 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: message->size() <= Channel::kMaximumMessageSize in ipc_channel_proxy.cc

Project Member Reported by ClusterFuzz, Nov 16

Issue description

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

Fuzzer: jsbell_serviceworker
Job Type: linux_cfi_chrome
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=570982:571001

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by ClusterFuzz, Nov 16

Components: Internals>Core
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

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

Comment 2 by ClusterFuzz, Nov 16

Cc: domfarolino@gmail.com yoichio@chromium.org
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

[LayoutNG] Not paint ellipsis selection by yoichio@chromium.org - https://chromium.googlesource.com/chromium/src/+/ba4cfa8ea85018176af83062b37cc2c44c2fb279

Remove RequestInit implementation in favor of IDL compiler's version by domfarolino@gmail.com - https://chromium.googlesource.com/chromium/src/+/b3559bebea6016d9fc5d825f47dd0837c2068145

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.
We don’t seem to be going down to core/fetch in the stacktrace at all, so I’m guessing my CL is not the culprit. Seems that the script execution somehow was failing?
Cc: -yoichio@chromium.org
Repro case doesn't relate to painting at all:
<script>
    (function() {
    }());
new Request("", { referrerPolicy: {bubbles: false}, redirect: Array(73538823)}, { integrity: Array()});;/* no-op */
</script>
Project Member

Comment 5 by ClusterFuzz, Nov 21

ClusterFuzz has detected this issue as fixed in range 596889:609905.

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

Fuzzer: jsbell_serviceworker
Job Type: linux_cfi_chrome
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=570982:571001
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=596889:609905

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

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.
Project Member

Comment 6 by ClusterFuzz, Nov 21

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 6001561798705152 is verified as fixed, so closing issue as verified.

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

Sign in to add a comment