Closed Bug 1638800 Opened 6 years ago Closed 6 years ago

Crash in [@ mozilla::ipc::MessageChannel::Send | mozilla::ipc::IProtocol::ChannelSend | IPC_Message_Name=PContent::Msg_SetClipboard]

Categories

(Core :: Widget, defect)

Unspecified
All
defect

Tracking

()

RESOLVED DUPLICATE of bug 1524237

People

(Reporter: gsvelto, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-7af5fb0b-495f-4f61-bd93-5ff710200516.

Top 10 frames of crashing thread:

0 XUL mozilla::ipc::MessageChannel::Send ipc/glue/MessageChannel.cpp:1007
1 XUL mozilla::ipc::IProtocol::ChannelSend ipc/glue/ProtocolUtils.cpp:471
2 XUL mozilla::dom::PContentChild::SendSetClipboard ipc/ipdl/PContentChild.cpp:4107
3 XUL nsClipboardProxy::SetData widget/nsClipboardProxy.cpp:36
4 XUL nsCopySupport::EncodeDocumentWithContextAndPutToClipboard dom/base/nsCopySupport.cpp:352
5 XUL mozilla::dom::Selection::NotifySelectionListeners dom/base/Selection.cpp:3144
6 XUL mozilla::dom::Selection::EndBatchChanges dom/base/Selection.cpp:3178
7 XUL mozilla::dom::Selection::SetStartAndEndInternal dom/base/Selection.cpp:3444
8 XUL mozilla::dom::Selection::SelectAllChildren dom/base/Selection.cpp:2667
9 XUL nsDocumentViewer::SelectAll layout/base/nsDocumentViewer.cpp:2551

Not sure if this is the right component because this crash seems to be happening at the intersection between the clipboard-handling code and the IPC code used to send the data.

We're crashing because of this assertion: MOZ_CRASH("IPC message size is too large"). Maybe very large clipboard operations need to be chunked up to avoid overflowing IPC messages? This seems to have started in version 76, the first crash we have on record has buildid 20200312093312.

I think this is a longstanding issue. If you search for crash reason raw with that, and signatures that contain "Clipboard", there's a bunch of similar-looking signatures.

Indeed, thanks. Bug 1524237 has an STR so I'll dupe against that.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.