gatsby-plugin-offline causing site to hang?
I'm testing my Gatsby site and have found a series of actions that cause it to hang in the browser. By "hang" I mean the browser is trying the load the site, the screen is blank, and the progress bar gets to about 75% and stops.
I am using gatsby-plugin-offline and suspect that its an issue with the service worker however, it is difficult to know for sure.
I have only been able to reproduce this hanging behavior on Android using Chrome. Chrome on the desktop doesn't have any issues nor does Firefox on Android. I think it has something to do with the way Chrome resumes.
Steps to reproduce
- Open Chrome
- Navigate to the site directly by typing url
- Kill Chrome
- Reopen Chrome
When I reopen Chrome, it tries to reload the site since it was open when I killed the app and this is where it hangs.
If I wait long enough (about 5 minutes) the site stops trying to load but the screen is still blank. It seems to hit some sort of timeout. At this point I am able to view the console through the remote debugging tools in Chrome on my desktop. Before this point, while it is still hanging, I can connect to the phone with the remote debugger but there is no browser detected which is partially why this has been so difficult to figure out. When I look at the console in the remote debugger it shows that a handful of resources have failed to load. They are not always the same ones that fail however some common ones include the following:
- webpack-runtime-xxxxxxxxxxxx.js
- app-xxxxxxxxxxxx.js
- component---node-modules-gatsby-plugin-offline-app-shell-js-xxxxxxxxxxxx.js
- https://fonts.googleapis.com/css?family=Poppins:400,600,700
All four of these items are in the cache as well as present on their respective host. The first three items are configured as precache items for WorkBox.
Final notes: There is nothing in the network tab of the debugger, just what I mentioned above from the console. If I refresh the site while it is hanging, or anytime, it works. Refresh always works, it's just when Chrome first opens that the site hangs.
Really strange stuff.
android 
google-chrome service-worker gatsby asked Jan 20 at 0:12
tleeftleef
2,04711728
add a comment |
I'm testing my Gatsby site and have found a series of actions that cause it to hang in the browser. By "hang" I mean the browser is trying the load the site, the screen is blank, and the progress bar gets to about 75% and stops.
I am using gatsby-plugin-offline and suspect that its an issue with the service worker however, it is difficult to know for sure.
I have only been able to reproduce this hanging behavior on Android using Chrome. Chrome on the desktop doesn't have any issues nor does Firefox on Android. I think it has something to do with the way Chrome resumes.
Steps to reproduce
- Open Chrome
- Navigate to the site directly by typing url
- Kill Chrome
- Reopen Chrome
When I reopen Chrome, it tries to reload the site since it was open when I killed the app and this is where it hangs.
If I wait long enough (about 5 minutes) the site stops trying to load but the screen is still blank. It seems to hit some sort of timeout. At this point I am able to view the console through the remote debugging tools in Chrome on my desktop. Before this point, while it is still hanging, I can connect to the phone with the remote debugger but there is no browser detected which is partially why this has been so difficult to figure out. When I look at the console in the remote debugger it shows that a handful of resources have failed to load. They are not always the same ones that fail however some common ones include the following:
- webpack-runtime-xxxxxxxxxxxx.js
- app-xxxxxxxxxxxx.js
- component---node-modules-gatsby-plugin-offline-app-shell-js-xxxxxxxxxxxx.js
- https://fonts.googleapis.com/css?family=Poppins:400,600,700
All four of these items are in the cache as well as present on their respective host. The first three items are configured as precache items for WorkBox.
Final notes: There is nothing in the network tab of the debugger, just what I mentioned above from the console. If I refresh the site while it is hanging, or anytime, it works. Refresh always works, it's just when Chrome first opens that the site hangs.
Really strange stuff.
android google-chrome service-worker gatsby asked Jan 20 at 0:12
tleeftleef
2,04711728
add a comment |
I'm testing my Gatsby site and have found a series of actions that cause it to hang in the browser. By "hang" I mean the browser is trying the load the site, the screen is blank, and the progress bar gets to about 75% and stops.
I am using gatsby-plugin-offline and suspect that its an issue with the service worker however, it is difficult to know for sure.
I have only been able to reproduce this hanging behavior on Android using Chrome. Chrome on the desktop doesn't have any issues nor does Firefox on Android. I think it has something to do with the way Chrome resumes.
Steps to reproduce
- Open Chrome
- Navigate to the site directly by typing url
- Kill Chrome
- Reopen Chrome
When I reopen Chrome, it tries to reload the site since it was open when I killed the app and this is where it hangs.
If I wait long enough (about 5 minutes) the site stops trying to load but the screen is still blank. It seems to hit some sort of timeout. At this point I am able to view the console through the remote debugging tools in Chrome on my desktop. Before this point, while it is still hanging, I can connect to the phone with the remote debugger but there is no browser detected which is partially why this has been so difficult to figure out. When I look at the console in the remote debugger it shows that a handful of resources have failed to load. They are not always the same ones that fail however some common ones include the following:
- webpack-runtime-xxxxxxxxxxxx.js
- app-xxxxxxxxxxxx.js
- component---node-modules-gatsby-plugin-offline-app-shell-js-xxxxxxxxxxxx.js
- https://fonts.googleapis.com/css?family=Poppins:400,600,700
All four of these items are in the cache as well as present on their respective host. The first three items are configured as precache items for WorkBox.
Final notes: There is nothing in the network tab of the debugger, just what I mentioned above from the console. If I refresh the site while it is hanging, or anytime, it works. Refresh always works, it's just when Chrome first opens that the site hangs.
Really strange stuff.
android google-chrome service-worker gatsby asked Jan 20 at 0:12
tleeftleef
2,04711728
I'm testing my Gatsby site and have found a series of actions that cause it to hang in the browser. By "hang" I mean the browser is trying the load the site, the screen is blank, and the progress bar gets to about 75% and stops.
I am using gatsby-plugin-offline and suspect that its an issue with the service worker however, it is difficult to know for sure.
I have only been able to reproduce this hanging behavior on Android using Chrome. Chrome on the desktop doesn't have any issues nor does Firefox on Android. I think it has something to do with the way Chrome resumes.
Steps to reproduce
- Open Chrome
- Navigate to the site directly by typing url
- Kill Chrome
- Reopen Chrome
When I reopen Chrome, it tries to reload the site since it was open when I killed the app and this is where it hangs.
If I wait long enough (about 5 minutes) the site stops trying to load but the screen is still blank. It seems to hit some sort of timeout. At this point I am able to view the console through the remote debugging tools in Chrome on my desktop. Before this point, while it is still hanging, I can connect to the phone with the remote debugger but there is no browser detected which is partially why this has been so difficult to figure out. When I look at the console in the remote debugger it shows that a handful of resources have failed to load. They are not always the same ones that fail however some common ones include the following:
- webpack-runtime-xxxxxxxxxxxx.js
- app-xxxxxxxxxxxx.js
- component---node-modules-gatsby-plugin-offline-app-shell-js-xxxxxxxxxxxx.js
- https://fonts.googleapis.com/css?family=Poppins:400,600,700
All four of these items are in the cache as well as present on their respective host. The first three items are configured as precache items for WorkBox.
Final notes: There is nothing in the network tab of the debugger, just what I mentioned above from the console. If I refresh the site while it is hanging, or anytime, it works. Refresh always works, it's just when Chrome first opens that the site hangs.
Really strange stuff.
android google-chrome service-worker gatsby android google-chrome service-worker gatsby asked Jan 20 at 0:12
tleeftleef
2,04711728
asked Jan 20 at 0:12
tleeftleef
2,04711728
asked Jan 20 at 0:12
tleeftleef
2,04711728
asked Jan 20 at 0:12
tleeftleef
2,04711728
asked Jan 20 at 0:12
tleeftleef
2,04711728
2,04711728
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54272493%2fgatsby-plugin-offline-causing-site-to-hang%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54272493%2fgatsby-plugin-offline-causing-site-to-hang%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
