gatsby: RangeError: Maximum call stack size exceeded - map-pages-to-static-query-hashes.js

I already tried everything 😦 From reset and remove /node_modules folder, the package-lock.json – as well as update gatsby-cli, and all my packages.

I’m stuck with this error that appears just before the development build process (that remains successful just for a bit) :

Here’s the shell output:

 ERROR 

Maximum call stack size exceeded



  RangeError: Maximum call stack size exceeded
  
  - map-pages-to-static-query-hashes.js:73 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:73:23
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9
  
  - map-pages-to-static-query-hashes.js:111 getDepsFn
    [myfoldername]/[gatsby]/dist/utils/map-pages-to-static-query-hashes.js:111:9

and this is my gatsby info --clipboard:

  System:
    OS: Linux 5.6 Arch Linux
    CPU: (4) x64 Intel(R) Core(TM) i3-5010U CPU @ 2.10GHz
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 14.3.0 - /usr/bin/node
    npm: 6.14.5 - /usr/bin/npm
  Languages:
    Python: 3.8.3 - /usr/bin/python
  npmPackages:
    gatsby: ^2.23.17 => 2.23.17
    gatsby-image: ^2.4.12 => 2.4.12
    gatsby-plugin-disqus: ^1.2.0 => 1.2.0
    gatsby-plugin-emotion: ^4.3.9 => 4.3.9
    gatsby-plugin-feed: ^2.5.10 => 2.5.10
    gatsby-plugin-google-gtag: ^2.1.9 => 2.1.9
    gatsby-plugin-layout: ^1.3.9 => 1.3.9
    gatsby-plugin-manifest: ^2.4.17 => 2.4.17
    gatsby-plugin-netlify-cache: ^1.2.0 => 1.2.0
    gatsby-plugin-offline: ^3.2.16 => 3.2.16
    gatsby-plugin-react-helmet: ^3.3.9 => 3.3.9
    gatsby-plugin-robots-txt: ^1.5.1 => 1.5.1
    gatsby-plugin-sharp: ^2.6.17 => 2.6.17
    gatsby-plugin-sitemap: ^2.4.10 => 2.4.10
    gatsby-plugin-svgr: ^2.0.2 => 2.0.2
    gatsby-plugin-typography: ^2.5.9 => 2.5.9
    gatsby-remark-images: ^3.3.17 => 3.3.17
    gatsby-remark-responsive-iframe: ^2.4.10 => 2.4.10
    gatsby-source-filesystem: ^2.3.17 => 2.3.17
    gatsby-transformer-remark: ^2.8.23 => 2.8.23
    gatsby-transformer-sharp: ^2.5.10 => 2.5.10
  npmGlobalPackages:
    gatsby-cli: 2.12.56

Thanks in advance for any help!

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 8
Comments: 16 (10 by maintainers)

Most upvoted comments

@pieh @freiksenet

This is my project (I created a stand alone instance to replicate the bug). As written in the README.md: in order to replicate the bug you need to do an explicit npm install gatsby@2.23.15 after the first npm intall.

https://github.com/anonimoconiglio/debug-blog

It’s ok if I let this debug instance only for a month online? I already stripped away all my posts, but still have concerns from a SEO point of view (don’t like the idea to have duplicated content online).

fsgreco on Jul 3, 2020

@anonimoconiglio try please:

    "gatsby": "2.23.5",
    "gatsby-cli": "2.12.54",

Hi @kondricz, gatsby@2.23.5 works 👍

fsgreco on Jul 2, 2020

I ran into this same crash loop following an update earlier today, so it isn’t isolated. A rollback resolved it.

The culprit is gatsby@2.23.15. The last working version for me is gatsby@2.23.14.

aaronadamsCA on Jul 2, 2020

@anonimoconiglio try please:

    "gatsby": "2.23.5",
    "gatsby-cli": "2.12.54",

kondricz on Jul 2, 2020

@mahtd @anonimoconiglio Excellent! Thank you for testing!

sidharthachatterjee on Jul 12, 2020

Just tried on my debug instance (the one I deploy to Github above), seems to work without problems!

The package went from “gatsby”: “^2.23.15” to “gatsby”: “^2.23.22-static-query-template.8”

fsgreco on Jul 7, 2020

Thank you for the report, we reverted the change and published new version 2.23.19.

freiksenet on Jul 3, 2020

(Note there might also be an ongoing npm ecosystem problem right now, because without my current package.lock file Gatsby is crashing with completely different errors than this one.)

aaronadamsCA on Jul 2, 2020