Bug 179748 - Crash in WebCore::SWServerJobQueue::didFinishInstall(WTF::ObjectIdentifier<WebCore::ServiceWorkerIdentifierType>, bool) + 62
Summary: Crash in WebCore::SWServerJobQueue::didFinishInstall(WTF::ObjectIdentifier<We...
Status: RESOLVED DUPLICATE of bug 179846
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-15 15:51 PST by Ryan Haddad
Modified: 2017-11-18 18:00 PST (History)
2 users (show)

See Also:


Attachments
Crash log (46.30 KB, text/plain)
2017-11-15 15:51 PST, Ryan Haddad
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Haddad 2017-11-15 15:51:02 PST
Created attachment 327030 [details]
Crash log

This flaky crash is seen with imported/w3c/web-platform-tests/service-workers/service-worker/shared-worker-controlled.https.html

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.WebCore             	0x00000001061e691e WebCore::SWServerJobQueue::didFinishInstall(WTF::ObjectIdentifier<WebCore::ServiceWorkerIdentifierType>, bool) + 62 (SWServerJobQueue.cpp:168)
1   com.apple.WebKit              	0x0000000103f12ae9 void IPC::handleMessage<Messages::WebSWServerToContextConnection::DidFinishInstall, WebKit::WebSWServerToContextConnection, void (WebCore::SWServerToContextConnection::*)(WTF::ObjectIdentifier<WebCore::ServiceWorkerIdentifierType>, bool)>(IPC::Decoder&, WebKit::WebSWServerToContextConnection*, void (WebCore::SWServerToContextConnection::*)(WTF::ObjectIdentifier<WebCore::ServiceWorkerIdentifierType>, bool)) + 78 (HandleMessage.h:127)
2   com.apple.WebKit              	0x0000000103c606e1 IPC::Connection::dispatchMessage(std::__1::unique_ptr<IPC::Decoder, std::__1::default_delete<IPC::Decoder> >) + 119 (Connection.cpp:930)
3   com.apple.WebKit              	0x0000000103c62e27 IPC::Connection::dispatchOneMessage() + 175 (Connection.cpp:959)
4   com.apple.JavaScriptCore      	0x00000001094479e4 WTF::RunLoop::performWork() + 164 (RunLoop.cpp:107)
5   com.apple.JavaScriptCore      	0x0000000109447c02 WTF::RunLoop::performWork(void*) + 34 (RunLoopCF.cpp:39)
6   com.apple.CoreFoundation      	0x00007fff95a167e1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
7   com.apple.CoreFoundation      	0x00007fff959f5f0c __CFRunLoopDoSources0 + 556
8   com.apple.CoreFoundation      	0x00007fff959f542f __CFRunLoopRun + 927
9   com.apple.CoreFoundation      	0x00007fff959f4e28 CFRunLoopRunSpecific + 296
10  com.apple.Foundation          	0x00007fff9244fcb9 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 270
11  com.apple.Foundation          	0x00007fff9244fb98 -[NSRunLoop(NSRunLoop) run] + 74
12  libxpc.dylib                  	0x00007fff88c11168 _xpc_objc_main + 751
13  libxpc.dylib                  	0x00007fff88c0fbbe xpc_main + 494
14  com.apple.WebKit.Storage      	0x0000000103c00702 main + 536
15  libdyld.dylib                 	0x00007fff879185ad start + 1

https://build.webkit.org/results/Apple%20El%20Capitan%20Release%20WK2%20(Tests)/r224899%20(6006)/results.html
Comment 1 Chris Dumez 2017-11-15 15:59:42 PST
Likely registration being null. This is similar to the other flaky crash we know about. My bet is that this is caused by us clearing all registrations between tests. If a registration had a pending install event (or fetch), then when that event completes, we'll come back to the StorageProcess and the registration will be gone by then.
Comment 2 Chris Dumez 2017-11-16 16:36:53 PST
I am hopping https://bugs.webkit.org/show_bug.cgi?id=179774 will fix this.
Comment 3 Ryan Haddad 2017-11-17 17:10:43 PST
(In reply to Chris Dumez from comment #2)
> I am hopping https://bugs.webkit.org/show_bug.cgi?id=179774 will fix this.
Still seeing this as of r224997: https://build.webkit.org/results/Apple%20El%20Capitan%20Release%20WK2%20(Tests)/r224997%20(6070)/results.html
Comment 4 Chris Dumez 2017-11-18 18:00:41 PST

*** This bug has been marked as a duplicate of bug 179846 ***