pwnall@: Could you triage this?

Able to reproduce the issue but issue is inconsistently seen. i.e; Issue is seen once in 10 times. Tested this issue on Samsung Galaxy J7/ Android 7

As issue is reproducible, marking as Untriaged for further inputs from dev team.

Thanks!

wanderview@: Any thoughts on M69 change could have caused this?

M69 was around the time I started.  The only thing that comes to mind was mojo-ification, but not sure exactly when that happened.  I'll try to reproduce when I return from travel.

Assigned to wanderview since he'll be taking the next step.

Do you need Flipkart Msite to reproduce the issue again? We are planning to add a workaround at our end to fix the issue. We have added a settimeout in case cache is not responding to fetch the content from the network and its working fine for us. Please let us know if we can go ahead and deploy the fix.

The NextAction date has arrived: 2018-11-19

I just tried to reproduce an I was not able to.  Did you already change the site?  Or do I need to be logged in to hit the service worker path?

I created an account, but I still can't reproduce.  Sometimes I get a slightly longer loading spinner, but it then progresses.  Feels like maybe the work around landed.

If that is the case I'll try to build an instrumented chrome to see if the cache requests are getting stuck somehow.  I have another high priority bug, though, so may not get to that until tomorrow.

We have actually added the workaround yesterday. Let us know if there is no other way to reproduce the issue, we will roll back the changes for 1 or 2 days. Thanks!

Do we have any update on this? Shall we go ahead and remove the fix for now?

Please leave your site fix in for now.  Last week was a holiday and I've had a bit of a delay getting an instrumented android setup.  If its an error in cache_storage, though, I should still be able to see it even if you are racing with network.

Note, if you are able to reproduce locally, you can also check if an error has been registered in:

chrome://histograms/ServiceWorkerCache

Attached is the histogram which we have got during the error. Please have a look.

Deleted: ServiceWorkerCache-Histogram.pdf 153 KB

ServiceWorkerCache-Histogram.pdf 153 KB Download

Thanks.  I don't see any errors in those histogram values, unfortunately.

There is a path that is sometimes hit where there is a very slow init.  Is it possible cache_storage is just being very slow, but does eventually return in your failure case.

I'm sorry I haven't been able to look at this more yet.  I have some high priority work I am stuck on at the moment.  I haven't forgotten about this bug, though.

So in error case page never loads. What we are trying from our side is, we will deploy the code which has an issue under AB. We will try to put you under AB and that might help you further debug the issue.

Its possible  bug 912141  would explain this if the device is under memory pressure and the disk operations are slow after reloading the browser.  Also very possibly unrelated, though.

I'm clearing SW as this looks like Cache Storage.

Nakul, does this still reproduce for you in chrome 72 (currently beta)?

We have not checked this on 72 but we will try that today and I will update the thread. Thanks!

Hi, we are able to reproduce the issue both in Chrome 71 stable version and 72 beta version.