RangeError - Maximum call stack size exceeded.
See original GitHub issueHi there,
I liked the API design of this library and decided to use it together with react-native-modalize
. It worked well locally, but in distribution builds the below error caused crashes on both iOS and Android.
I switched to another library and unfortunately can’t put time into creating a bare minimum reproducible case. But I thought I’d share it!
RangeError
Maximum call stack size exceeded.
node_modules/immer/dist/immer.esm.js:1:712 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
node_modules/immer/dist/immer.esm.js:1:782
[native code] forEach
node_modules/immer/dist/immer.esm.js:1:745 i
node_modules/immer/dist/immer.esm.js:1:2562 M
node_modules/immer/dist/immer.esm.js:1:3055 A
node_modules/immer/dist/immer.esm.js:1:2588
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:36 (16 by maintainers)
Top 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 >Uncaught RangeError: Maximum call ... - Net-Informations.Com
This error is almost always means you have a problem with recursion in JavaScript code, as there isn't any other way in JavaScript...
Read more >JavaScript Error: Maximum Call Stack Size Exceeded
If you see the “Maximum Call Stack Size Exceeded” error, there's likely a problem with a recursive function within your JavaScript code.
Read more >RangeError: Maximum call stack size exceeded - Educative.io
The most common source for this error is infinite recursion. You must have a recursive function in your code whose base case is...
Read more >RangeError: Maximum call stack size exceeded in JavaScript
The "RangeError: Maximum call stack size exceeded" error occurs when a function is called so many times that the invocations exceed the call...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was using react
context provider
inside thePortal
component, and I was getting this issue in a release build only like above. When I moved thecontext provider
to the outside of thePortalHost
. Because I’m using the portal host at a different layer than the root host. Then I no longer had this issue. I don’t know what would cause this, but ill try to create a reproducible expo demo tomorrow. Ill update where I get to.this should be fixed with
v1.0.9
, thanks to @egadstar PR 👏