Bug 188796 - Service Worker Crashes
Summary: Service Worker Crashes
Status: RESOLVED DUPLICATE of bug 185653
Alias: None
Product: WebKit
Classification: Unclassified
Component: Service Workers (show other bugs)
Version: Safari 11
Hardware: Mac macOS 10.13
: P2 Major
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-21 09:13 PDT by Greg Wardwell
Modified: 2018-08-21 15:48 PDT (History)
1 user (show)

See Also:


Attachments
A crash log generated from Safari Service Worker crash (98.41 KB, text/rtf)
2018-08-21 09:13 PDT, Greg Wardwell
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Wardwell 2018-08-21 09:13:31 PDT
Created attachment 347647 [details]
A crash log generated from Safari Service Worker crash

I work on the team running https://www.sweetwater.com where rolled out a Service Worker in February. Around July 14 we began receiving reports from company employees that they were experiencing Service Worker crashes with the message "Safari Service Worker quit unexpectedly". The pattern was that on each Mac Mini that the error occurred on, a random but consistent URL would yield a hard crash of the Service Worker process. While we were unable to duplicate the issue on our developer team, we looked at the evidence and tried pushing a version of our Service Worker with a cache expiry to production. That change, along with instructing employees to clear their site data for Sweetwater.com, seems to have (temporarily?) alleviated the issue.

I've attached an error log from one of those crashes to this but report.
Comment 1 Alexey Proskuryakov 2018-08-21 15:33:03 PDT
Thank you for the report!

This crash log matches the problem fixed in bug 185653. The fix is present in Safari Technology Preview, but it hasn't been included into any shipping releases yet.

*** This bug has been marked as a duplicate of bug 185653 ***
Comment 2 Greg Wardwell 2018-08-21 15:48:42 PDT
Thanks for the fast response. Iā€™m glad to see that this has been taken care of, but are there any steps we can take to mitigate this issue while we wait for the fix to be released beyond the technology preview?