<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - fast/dom/rtl-scroll-to-leftmost-and-resize.html is a flaky timeout - IPC drops messages"
href="https://bugs.webkit.org/show_bug.cgi?id=148951#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - fast/dom/rtl-scroll-to-leftmost-and-resize.html is a flaky timeout - IPC drops messages"
href="https://bugs.webkit.org/show_bug.cgi?id=148951">bug 148951</a>
from <span class="vcard"><a class="email" href="mailto:ap@webkit.org" title="Alexey Proskuryakov <ap@webkit.org>"> <span class="fn">Alexey Proskuryakov</span></a>
</span></b>
<pre>Okay, a little less mysterious. We do get the message in Connection::processIncomingMessage in UI process, but in the failing case, it gets processed by this block:
// Check if we're waiting for this message.
{
std::lock_guard<Lock> lock(m_waitForMessageMutex);
if (m_waitingForMessage && m_waitingForMessage->messageReceiverName == message->messageReceiverName() && m_waitingForMessage->messageName == message->messageName() && m_waitingForMessage->destinationID == message->destinationID()) {
m_waitingForMessage->decoder = WTF::move(message);
ASSERT(m_waitingForMessage->decoder);
m_waitForMessageCondition.notifyOne();
return;
}
...
So, Connection::waitForAndDispatchImmediately must be buggy, the message that it's waiting for can get dropped altogether.
Once a DidUpdateGeometry message gets dropped, that makes UI process never again send any DrawingArea::UpdateGeometry messages for this drawing area.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>