Gatsby: Bug? on official website

Created on 21 Nov 2018 · 12Comments · Source: gatsbyjs/gatsby

Description

Here is a gif:

nov-21-2018 20-42-26

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)

bug

Source

sidbentifraouine

👍2

All 12 comments

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.
gatsby_malformed_url

jonniebigodes on 21 Nov 2018

👍1

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?

jgierer12 on 21 Nov 2018

@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

jonniebigodes on 21 Nov 2018

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

jgierer12 on 21 Nov 2018

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.

sidbentifraouine on 21 Nov 2018

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.
gatsby_malformed_url_cache_size

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

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

jonniebigodes on 21 Nov 2018

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 :)

davidbailey00 on 21 Nov 2018

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).

pieh on 21 Nov 2018

The issue still exists

tigrankhachikyan on 26 Nov 2018

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

davidbailey00 on 26 Nov 2018

@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 :)

tigrankhachikyan on 27 Nov 2018

👍1

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.