Tried testing the issue reported chrome version #70.0.3535.0 using Windows 10 by following below steps.

Steps:
=====
1.Launched chrome.
2.Navigated to 'https://editor.construct.net/r114/'.
3.Opened dev tools under  the Application tab selected 'Clear storage'. 
4.Selected everything and clicked 'Clear site data'.
5.Reloaded the main page.
6.Checked the console and network tabs but unable to see any errors.
7.Closed devtools and repeated step#2, Step#3, Step#4 and Step#5.
8.Waited for 10seconds and opened the console and network.
9.Observed that under console tab unable to see 'all resouces saved and offline support is ready' and under network tab could not see any request.

Attached screencast for reference.
@Reporter: Could you please review the attached screen-cast and confirm if anything being missed here.
Thanks.!

Deleted: 878422.mp4 4.4 MB

	878422.mp4 4.4 MB View Download

You didn't follow the repro steps right: you're meant to leave devtools open to reproduce the issue, but you closed it.

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

Thanks for reporting this!
I'm seeing a couple bugs around fetch event, and I'm suspecting this issue is related to  issue 878667  or  issue 879069 .

It is possible but the original report says it reproduces in stable 68 which shouldn't be affected by those issues unless ServiceWorkerServicification or NetworkService is enabled via chrome://flags.

For what it's worth I couldn't reproduce on Mac 70 with ServiceWorkerServicification enabled.

I tried again in 70.0.3535.4 on Mac with ServiceWorkerServicification disabled this time and still can't repro this.

ash@scirra, could you provide a NetLog?
https://dev.chromium.org/for-testers/providing-network-details

Managed to reproduce and capture a NetLog in Canary 70.0.3537.0: https://www.dropbox.com/s/ferkrhv352vux7x/chrome-net-export-log.zip?dl=0
Also attached two screenshots showing lists of failed requests, and the headers for the first failed request.

This is tough to reproduce because it seems the "Clear site data" button doesn't always work. Sometimes when I click that and reload the tab the SW then reports "Up to date", which is what would happen if all the data was left behind and the page reloaded. It seems you need to retry a couple of times before it happens.

Thanks. Unfortunately the netlog doesn't seem to capture the failed loads. I just see one event "HTTP_SERVER_PROPERTIES" when I open it in chrome://net-internals -> Import.

I notice in the screenshot "Disable cache" is selected in DevTools. Is that needed to reproduce the issue for you?

also the netlog says it's from 68.0.3440.106 rather than 70.0.3537.0... is it the wrong netlog?

Tried testing the issue as per comment #4 on chrome version #70.0.3537.0. Observed no errors in console and no failed requests under network tab which was mentioned in comment#0-Step4.

Attached screencast for reference.
@reporter: Could you please review the screencas and let us know if anything is being missed here. If possible request you provide screencast of the issue, so that it would be really helpful for better triaging of the issue.As per comment#6, could you please confirm whether the issue is related to  issue 878667  or  issue 879069 .

Thanks.!

Deleted: 878422_New.mp4 18.3 MB

878422_New.mp4 18.3 MB Download

I've also been seeing an issue like this (on Mac, 69.0.3497.72) - all requests will hang waiting for the service worker, they will all be in the pending state in devtools.

This seems to happen not on the initial page load, but after a short period of time, and once this bug is triggered I can't load the site in new tabs either.

I put a breakpoint on the event listener in the serviceworker for 'fetch' and when this  issue is happening, the event listener is not called, as soon as the issue comes right then the breakpoint fires so I know the breakpoint is working.

This seems to sometimes fix itself after a few minutes, and it seems that also pressing the test sync button in the Application -> Service worker tab in devtools would wake up the service worker and fix it.

I'll record a screencast next time this happens for me.

Here's a screencast: https://www.youtube.com/watch?v=3VObX47W9Uc&feature=youtu.be

It looks to me like this is related to 878667 , though I'm not sure if they realised the impact could be this large.

Yes c#13 sounds exactly like  issue 878667 . I thought the original issue reported here is different because the report says it reproduces on stable Chrome 68 which shouldn't be affected by  issue 878667 .

Chrome updated to 69.0.3497.81 so I tested again with that. I could definitely reproduce the issue once, but it seems random and trying a couple of dozen times after that I couldn't reproduce it again. So I've been unable to get a NetLog so far.

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

Thanks for the update.

As per comment #15, this issue is similar to  issue 878667 . Hence merging this to  issue 878667 .
Please feel free to undupe if it is not the case.

Thanks..