question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Errors even when no code present: Call stack size / cannot read property

See original GitHub issue

Description

I have an issue I need help with that seems to have popped up a few times over the years. I have burned 8 hours, one full work day, and this is too much.

Backstory: Have a working page that needed updates. Unfortunately for some reason, after 2.5 months of no updates and no changes, it has stopped building, on both netlify and local development, throwing either a) RangeError: Maximum call stack size exceeded b) TypeError: Cannot read property 'internal' of null

Steps to reproduce

  • Clone https://github.com/inblock-io/inblock
  • npm install
  • you will need the following add these access tokens to (these are Ok to post> spaceid: lil8n4syivvk , content api access token: rJ6yJJXuukb5K7ghg761Aj0w0rvcOKTwSeKHxcztYLI) to the .contentful.json.sample file in the project root and REMOVE the .sample extension

Expected result

npm run dev -> content pulled from contentful, everybody happy, page is served

Actual result

a) RangeError: Maximum call stack size exceeded b) TypeError: Cannot read property 'internal' of null

Environment

System: OS: Windows 10 10.0.19041 CPU: (12) x64 Intel® Core™ i7-8750H CPU @ 2.20GHz Binaries: Node: 10.13.0 - C:\Program Files\nodejs\node.EXE npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD Browsers: Chrome: 86.0.4240.75 Edge: Spartan (44.19041.423.0), Chromium (86.0.622.38) npmPackages: gatsby: ^1.9.279 => 1.9.279 gatsby-image: ^1.0.55 => 1.0.55 gatsby-link: ^1.6.46 => 1.6.46 gatsby-plugin-react-helmet: ^1.0.8 => 1.0.8 gatsby-plugin-sharp: ^1.6.46 => 1.6.48 gatsby-source-contentful: ^1.3.54 => 1.3.54 gatsby-transformer-remark: ^1.7.44 => 1.7.44 npmGlobalPackages: gatsby: 2.24.53

Commentary

1st I thought it might be this behind it: https://github.com/gatsbyjs/gatsby/blob/639a0ca2cffc8009602b808cc165c74ff4ce5dc5/packages/gatsby-plugin-react-helmet/README.md#compatibility-with-react-168-useeffect-hook

How can I find out what the hell is going on? If this is an offending, failing graphQL query, how do i troubleshoot if I cannot even get graphiql locally?

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:10

github_iconTop GitHub Comments

1reaction
axe312gercommented, Dec 10, 2020

@le-dawg thank you! reopening!

0reactions
github-actions[bot]commented, Feb 9, 2021

Hey again!

It’s been 60 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to comment on this issue or create a new one if you need anything else. As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community! 💪💜

Read more comments on GitHub >

github_iconTop Results From Across the Web

javascript - Maximum call stack size exceeded error
It means that somewhere in your code, you are calling a function which in turn calls another function and so forth, until you...
Read more >
JavaScript RangeError: Maximum Call Stack Size Exceeded
The JavaScript RangeError: Maximum call stack size exceeded is an error that occurs when there are too many function calls, or if a...
Read more >
How to Read React Errors (fix 'Cannot read property of ...
Cannot read property means the code was trying to read a property. This is a good clue! There are only a few ways...
Read more >
Errors | Node.js v19.3.0 Documentation
The Error.stackTraceLimit property specifies the number of stack frames collected by a stack trace (whether generated by new Error().stack or Error.
Read more >
Common JavaScript Debugging Problems and How to ...
This is one of the most common JavaScript errors, and it usually happens when there is a non-existent variable referenced somewhere in the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found