Bug 124459 - Assertion failure (!privateBrowsingStorageSessionIdentifierBase().isNull()) in RemoteNetworkingContext::ensurePrivateBrowsingSession() running the API tests after WebKit2.PrivateBrowsingPushStateNoHistoryCallback
Summary: Assertion failure (!privateBrowsingStorageSessionIdentifierBase().isNull()) i...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit2 (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-16 12:40 PST by mitz
Modified: 2013-12-13 10:20 PST (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mitz 2013-11-16 12:40:23 PST 
Running TestWebKitAPI with a debug build causes an assertion failure in the Networking process:

ASSERTION FAILED: !privateBrowsingStorageSessionIdentifierBase().isNull()
Source/WebKit2/NetworkProcess/mac/RemoteNetworkingContext.mm(111) : static void WebKit::RemoteNetworkingContext::ensurePrivateBrowsingSession()
1   0x1085e7aa0 WTFCrash
2   0x106994a6a WebKit::RemoteNetworkingContext::ensurePrivateBrowsingSession()
3   0x1068656f2 WebKit::NetworkProcess::initializeNetworkProcess(WebKit::NetworkProcessCreationParameters const&)
4   0x1068728a7 void CoreIPC::callMemberFunction<WebKit::NetworkProcess, void (WebKit::NetworkProcess::*)(WebKit::NetworkProcessCreationParameters const&), WebKit::NetworkProcessCreationParameters>(std::__1::tuple<WebKit::NetworkProcessCreationParameters>&&, WebKit::NetworkProcess*, void (WebKit::NetworkProcess::*)(WebKit::NetworkProcessCreationParameters const&))
5   0x106871950 void CoreIPC::handleMessage<Messages::NetworkProcess::InitializeNetworkProcess, WebKit::NetworkProcess, void (WebKit::NetworkProcess::*)(WebKit::NetworkProcessCreationParameters const&)>(CoreIPC::MessageDecoder&, WebKit::NetworkProcess*, void (WebKit::NetworkProcess::*)(WebKit::NetworkProcessCreationParameters const&))
6   0x106871270 WebKit::NetworkProcess::didReceiveNetworkProcessMessage(CoreIPC::Connection*, CoreIPC::MessageDecoder&)
7   0x10686547a WebKit::NetworkProcess::didReceiveMessage(CoreIPC::Connection*, CoreIPC::MessageDecoder&)
8   0x106759153 CoreIPC::Connection::dispatchMessage(CoreIPC::MessageDecoder&)
9   0x106751810 CoreIPC::Connection::dispatchMessage(std::__1::unique_ptr<CoreIPC::MessageDecoder, std::__1::default_delete<CoreIPC::MessageDecoder> >)
10  0x106758ee1 CoreIPC::Connection::dispatchOneMessage()
11  0x106765862 WTF::FunctionWrapper<void (CoreIPC::Connection::*)()>::operator()(CoreIPC::Connection*)
12  0x1067657e5 WTF::BoundFunctionImpl<WTF::FunctionWrapper<void (CoreIPC::Connection::*)()>, void (CoreIPC::Connection*)>::operator()()
13  0x10676d302 WTF::Function<void ()>::operator()() const
14  0x10676d27c std::__1::__function::__func<WTF::Function<void ()>, std::__1::allocator<WTF::Function<void ()> >, void ()>::operator()()
15  0x10861000a std::__1::function<void ()>::operator()() const
16  0x10861faa4 WTF::RunLoop::performWork()
17  0x108620f54 WTF::RunLoop::performWork(void*)
18  0x7fff90a248f1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__
19  0x7fff90a16062 __CFRunLoopDoSources0
20  0x7fff90a157ef __CFRunLoopRun
21  0x7fff90a15275 CFRunLoopRunSpecific
22  0x7fff93155a7c -[NSRunLoop(NSRunLoop) runMode:beforeDate:]
23  0x7fff9323e70a -[NSRunLoop(NSRunLoop) run]
24  0x7fff880efc2f _xpc_main
25  0x7fff91a53b2e xpc_main
26  0x105593375 main
27  0x7fff8b04e5fd start

I am not sure which test(s) are triggering this.
Comment 1 mitz 2013-12-13 10:07:16 PST 
You can reproduce this by running just two tests:
TestWebKitAPI --gtest_filter=WebKit2.GetPIDAfterAbortedProcessLaunch:WebKit2.PrivateBrowsingPushStateNoHistoryCallback
Comment 2 mitz 2013-12-13 10:20:39 PST 
I think this is caused by mixing tests that use the network process with tests that don’t.