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.

"too much recursion" after introduction of fast-deep-equal

See original GitHub issue

After update to 0.1.72 we get “too much recursion” on equal() call. The error seems pretty random, e.g. we add a line to package.json for jest configuration and then we remove it, and one of the webpack builds exhibits the problem, and the other doesn’t (while the line is unrelated to the build).

We pass only very basic props to SplitPane (no deeply nested, recursive structures). children of SplitPane contain one redux-connected component (but a simple one, too).

too much recursion[Learn More] index.js:4
"The above error occurred in the <Pane> component:
in Pane (created by SplitPane)
in div (created by SplitPane)
in SplitPane (created by SplitPaneView)
in div (created by SplitPaneView)
in SplitPaneView (created by Connect(SplitPaneView))
in Connect(SplitPaneView) (created by X)
in div (created by X)
in X (created by App)
in Y (created by Connect(Y))
in Connect(Y) (created by App)
in Z (created by Connect(Z))
in Connect(Z) (created by App)
in div (created by App)
in App (created by Root)
in Provider (created by Root)
in Root

Browser: Firefox 57.0.1 (64-bit)

As a side note: it would be really helpful if the repo was tagged for releases.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:10 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
tomkpcommented, Dec 21, 2017

@ndelangen thanks for helping (it’s always appreciated!), I’ll try and take a look into it…

0reactions
rajsekcommented, Dec 25, 2017

Hi @ndelangen I created this online stackblitz IDE, to replicate the issue with a simple setup (with react, redux and react-split-pane@0.1.72 version).

If possible, please help me to replicate the issue using any of below two ways

  1. Use the online IDE code, update and share me the code setup which produces “too much recursion” error. or
  2. if possible push the minimal POC code to replicate the issue and share me the GitHub URL for further investigation.

Regards, D.Raja Sekar

Read more comments on GitHub >

github_iconTop Results From Across the Web

InternalError: too much recursion - JavaScript - MDN Web Docs
The JavaScript exception "too much recursion" or "Maximum call stack size exceeded" occurs when there are too many function calls, or a function...
Read more >
JavaScript: Too much recursion? - Stack Overflow
Javascript has a build-in method to test if something is dividable with something else, called modulus ( % ).
Read more >
Recursion and stack - The Modern JavaScript Tutorial
So, the recursion reduces a function call to a simpler one, and then – to even more simpler, and so on, until the...
Read more >
Poor Treatment of Recursion in Introductory Textbooks, and a ...
In general, unbounded recursion is bad. Most recursion can be rewritten to be iterative. The cause of the problem, though, was that Ruby...
Read more >
Brief Introduction to Recursion - Medium
After that call the recursive function performs nothing. The function has to process or perform any operation at the time of calling and...
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