1263763 - Browser hang in IPC::Channel::ChannelImpl::ProcessIncomingMessages

Status: RESOLVED DUPLICATE of bug 1264398

(Core :: IPC, defect)

Description

[Andrew McCreight [:mccr8]]

Attachment: hang stack

The_8472 in IRC reported that after using the browser for an hour or so, it would become completely unresponsive. Using WinDBG, they were able to get a stack which looks intriguingly related to bug 1235633. Off-hand, I'd guess this is a dupe of bug 1263457, but I figured I'd file this separately in case it is not.

ChannelImpl::ProcessIncomingMessages is calling realloc, and it looks like the new size is 0x81e958, which Google tells me is 8513880.

Comment 1

[Jim Mathies [:jimm]]

The IO thread stack isn't of much use here unfortunately.

Comment 2

[The 8472]

Some more details:

* win64 nightly
* main thread was more or less idle during the hang
* the attached thread was the busy one. it spent most of its time in sys and not in user

Comment 3

[Andrew McCreight [:mccr8]]

ni? to Bill to be sure he sees it.

Comment 4

[The 8472]

Dragging large images also consumes huge amounts of system CPU time.

E.g. opening https://upload.wikimedia.org/wikipedia/commons/d/db/Greatwall_large.jpg in a new tab and then starting to drag the image causes a background thread to consume 100% CPU and the drag preview to show up with a large delay.

Comment 5

[Andrew McCreight [:mccr8]]

That makes some sense. Drag and drop can involve some very large messages, as seen here in Msg_InvokeDragSession: http://mzl.la/25ZRaV5

Comment 6

[Andrew Overholt [:overholt]]

Potential dupe of bug 1264398.

Comment 7

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

This is almost certainly a dupe.