"Maximum call stack size exceeded." triggered by version 0.0.18 [iOS]
See original GitHub issuePlatform: iOS only; [Android is OK]
We’ve just upgraded to redux-persist-transform-filter: 0.0.18 and the following error is thrown. Unfortunately, the call stack isn’t very useful.
Maximum call stack size exceeded.
initCloneObject
index.js:1253:66
baseClone
index.js:869:31
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
cloneMap
index.js:1030:33
initCloneByTag
index.js:1290:22
baseClone
index.js:877:30
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
cloneMap
index.js:1030:33
initCloneByTag
index.js:1290:22
baseClone
index.js:877:30
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
cloneMap
index.js:1030:33
initCloneByTag
index.js:1290:22
baseClone
index.js:877:30
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
baseClone
index.js:891:12
<unknown>
index.js:897:39
arrayEach
index.js:140:17
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
JavaScript RangeError: Maximum Call Stack Size Exceeded
The RangeError: Maximum call stack size exceeded is thrown when a function call is made that exceeds the call stack size. This can...
Read more >React Native iOS build release: RangeError: Maximum call ...
I have started to get this issue right after installing "@react-native-async-storage/async-storage" and I see thet you have this packeg also.
Read more >maximum call stack size exceeded typescript - You.com
The RangeError: Maximum call stack size exceeded occurs when a function is being called so many times that the invocations exceed the call...
Read more >"RangeError: Maximum call stack size exceeded" after Unity ...
when I try to run on safari or chrome on an iPhone 7 running ios version 13.1.1 it does not load. Code (CSharp):....
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 >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 FreeTop 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
Top GitHub Comments
We finally managed to track the issue down on RN 0.57.5 . Created an issue with lodash.clonedeep as well.
Reverting to 0.0.17 fixes the problem.
yeah, i think that would be the best solution. the thing is, i didn’t want to manipulate the state directly, so I deepcloned it.