Service worker registration + Clear-Site-Data + SW dev tools open hangs all requests
Reported by
asa.kus...@gmail.com,
Dec 19
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Steps to reproduce the problem: Video reproduction: https://www.youtube.com/watch?v=4mnRrrke8-g Reproduction app: https://github.com/asakusuma/sw-clear-site-data/tree/re-register-bug 1. Open http://localhost:3000 in Chrome Canary 2. Open the service worker tab of the dev tools. 3. Click the "Register service worker" button 4. Refresh the page a couple times 5. Click the "Turn on Clear-Site-Data" button 6. Refresh the page a couple times 7. Click the "Register service worker" button 8. Refresh the page What is the expected behavior? The refresh should reload the page as usual What went wrong? The request to refresh hangs and never complete. The bug does not happen if the service worker dev tools tab is not open. Did this work before? N/A Chrome version: 73.0.3645.0 Channel: stable OS Version: OS X 10.14.2 Flash Version: Might be related to https://bugs.chromium.org/p/chromium/issues/detail?id=898465
,
Dec 19
Forgot to mention that unregistering the service worker from chrome://serviceworker-internals doesn't recover from the problem, but restarting the browser does.
,
Dec 20
,
Dec 20
Unable to reproduce the issue on reported chrome version #73.0.3645.0 using Mac 10.14.1 by following below steps. Steps: ===== 1.Launched chrome. 2.Started a local server. 3.Navigated to "localhost:8000". 4.Opened the html page and Devtools->Network tab. 5.Clicked on "Register service worker" button. 6.Refreshed the page for couple of times. 7.Clicked on "Turn on Clear-Site-Data" button. 8.Again refreshed the page couple of times. 9.Clicked on "Register service worker" button and refreshed the page. 10.Observed that page loaded without hanging. Attached screencast for reference. @reporter:Could you please review attached screencast and let us know if anything is being missed here. Requesting you to retry the issue by creating a new profile without any apps and extensions in it, reset all flags to default and let us know if issue still persists. Thanks.!
,
Dec 20
,
Dec 21
In the screencast, the service worker tab of the dev tools is not open. This is a critical step in reproducing the error. I created a new profile without any apps or extensions and I do not have any flags turned on. While re-testing, I realize that you actually have to start out on the network tab and then move over to the service worker tab to reproduce, just like I did in the screencast. So the screencase I made has to be followed exactly, with each functional test mirrored with the right dev tools tab open.
,
Dec 21
To be clear, I can still reproduce the error with the new profile. But I realize the written repro steps are a bit off. Step 2 should actually be to open the network tab. And there should be a step between 6 and 7 which is to go from the network dev tools tab to the service worker dev tools tab.
,
Dec 21
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 7
Rewording the repro steps according to comment #7: 1. Open http://localhost:3000 in Chrome Canary 2. Open the DevTools>Network tab of the dev tools. 3. Click the "Register service worker" button 4. Refresh the page a couple times 5. Click the "Turn on Clear-Site-Data" button 6. Refresh the page a couple times 7. Go from DevTools>Network to DevTools>Application>Service worker 8. Click the "Register service worker" button 9. Refresh the page What is the expected behavior? The refresh should reload the page as usual What went wrong? The request to refresh hangs and never complete.
,
Jan 7
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by asa.kus...@gmail.com
, Dec 19