[Webkit-unassigned] [Bug 182991] New: ASSERT under WebAutomationSession::setProcessPool() when running W3C test suite a second time

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=182991

            Bug ID: 182991
           Summary: ASSERT under WebAutomationSession::setProcessPool()
                    when running W3C test suite a second time
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebDriver
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: bburg at apple.com
                CC: aestes at apple.com, bburg at apple.com, cgarcia at igalia.com,
                    joepeck at webkit.org, timothy at hatcher.name

It appears that the WebProcessPool's WebAutomationSession did not get cleared properly before we set the next one. Thus, we hit this assertion:

#1      0x000000010f8cf13e in IPC::MessageReceiverMap::addMessageReceiver(IPC::StringReference, IPC::MessageReceiver&) at /Users/bburg/repos/webkit/OpenSource/Source/WebKit/Platform/IPC/MessageReceiverMap.cpp:44

    ASSERT(!m_globalMessageReceivers.contains(messageReceiverName));

Because the old session has still registered for the name "WebAutomationSession". I looked into the receiver map and saw some unrecognized pointer still registered for that name. So, my hunch is that it's an old session that wasn't cleared properly. In general, the existing pattern of relying on the destructor to run at a certain time and clean up message receivers seems bad. If the client accidentally retained the WebAutomationSession somehow, then this would behave poorly.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180221/e6b2ba51/attachment.html>