[Webkit-unassigned] [Bug 186653] New: Add release assertion against destroying WebProcessPool from networkProcessFailedToLaunch callback
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Jun 15 04:33:12 PDT 2018
https://bugs.webkit.org/show_bug.cgi?id=186653
Bug ID: 186653
Summary: Add release assertion against destroying
WebProcessPool from networkProcessFailedToLaunch
callback
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: WebKit2
Assignee: webkit-unassigned at lists.webkit.org
Reporter: koivisto at iki.fi
Looks like some clients manage to tear down WebProcessPool from processDidClose callback. Add assertion to find out how.
Thread[0] EXC_BAD_ACCESS (SIGSEGV) (KERN_INVALID_ADDRESS at 0x0000000000000000)
[ 0] 0x000000023482c8fc WebKit`WebKit::WebProcessPool::networkProcessFailedToLaunch(WebKit::NetworkProcessProxy&) + 76 at WebProcessPool.cpp:548:21
544 ASSERT(&networkProcessProxy == m_networkProcess.get());
545 m_didNetworkProcessCrash = true;
546
547 for (auto& supplement : m_supplements.values())
-> 548 supplement->processDidClose(&networkProcessProxy);
--
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/20180615/1551852e/attachment.html>
More information about the webkit-unassigned
mailing list