Bug? on official website

[sidalidev]

Description

Here is a gif:

Steps to reproduce

Go to this link `https://www.gatsbyjs.org/starters/gatsby-starter-blog/?gatsby-

Environment

Chrome on Mac Mojave
Version 70.0.3538.102 (Official Build) (64-bit)

[jonniebigodes]

As the url is malformed, you're trying to inject a query param and when gatsby tries to render it will throw what is in the image bellow.

[jgierer12]

I am not able to reproduce this on the same Chrome version on Windows 10. Just wanted to point out that the URL you linked doesn't match the one in your GIF (missing 404 at the end). Is that intentional?

[jonniebigodes]

@jgierer12 i just did, the image i posted is a screen grab from windows 10 with chrome and it does that.
I will clear my cache for the gatsby site and retry it to see if it will make the cache soar like the chrome process on my machine

[jgierer12]

Hmm, I still can't reproduce. Tried with ?gatsby- and ?gatsby-404, as well as full and empty cache.

[sidalidev]

I have the same issue on Firefox 63.0.3 (64-bit), it works on Chrome in Incognito mode, but i blinks 3-4 times before loading correctly.

[jonniebigodes]

More on the issue at hand.
After leaving the url opened for a bit this is the my data on the gatsby app.
It starts to grow and with that the chrome process going through the roof.

After clearing the cache and revisiting the url is what the dev console throws.

Also it goes from the url provided to gatsby-404 and back. It will loop between the two urls never ending, even in incognito.

[vtenfys]

Hey there, the root cause of this is your adblocker blocking resources (since they contain the word "ad") but next week I'll write a fix which checks for multiple failures to prevent infinite reloading :)

[pieh]

Soooo, while we shouldn't blink like that - that's a bug - the reason why this is happening is because path to results of page query is https://www.gatsbyjs.org/static/d/762/path---starters-gatsby-starter-blog-ad-4-976-0MqaLzYKDy4oEO6kqu9wdOsLoU.json (it contains ad which adblocker then blocks - thanks @davidbailey00 for pointing it out).

And because we fail to get all resources we then do this: https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/cache-dir/ensure-resources.js#L98-L111 which we will need to be better at so we don't do inifinite reload (like in the gif).

[tigrankhachikyan]

The issue still exists

[vtenfys]

@tigrankhachikyan Hence why it is still open :) I'm just going to try fixing this now!

[tigrankhachikyan]

@tigrankhachikyan Hence why it is still open :) I'm just going to try fixing this now!

Sorry, I saw Closed above, and didn't noticed that it is for a duplicate issue.
Very sorry :)

[pushkar8723]

I ran into this issue and thought to leave a comment in case anyone else is still facing it.

I forked my repo from gatsby starter blob and this happened to me when I did a gatsby build to figure out some build failure on the server and then switched back to npm run develop. I figured out that it was because of the service worker and just unregistering it and reloading fixes the issue.