-
Notifications
You must be signed in to change notification settings - Fork 7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RangeError: Maximum call stack size exceeded #978
Comments
Yap, many recursive methods are susceptible to call stack limits which vary for enviros and func too size. It's not a common enough problem to address at the moment (would mean large perf hits for an edge issue) |
@mgcrea can you gist the object your iterating over. |
@jdalton https://gist.github.com/mgcrea/523ef0ea0b37ee9b330b Fixed it with this for now, looks like to be working:
[edit] Might be more reusable as JSONs https://gist.github.com/mgcrea/5881666f7c71280b758c |
These objects are tiiiiny. I'll dig in this evening. |
Indeed, the base test-case does crash and is only merging two strings:
Might help:
|
The method isn't intended for strings so I think its probably iterating them as a string object (so iterating the index proprerties of both strings) |
This is a bug on |
Added tests 89ed40e. |
Ran into this as well with a defaultsDeep implementation when upgrading from 2.4.1 to 3.2. |
Expect a bump, 3.3.0, by Friday evening. |
Thanks! |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Probably not a bug but I got some weird error after upgrading from
~v2.4
, haven't really dug into yet but it might help anyone encountering this suddenly:Using a "standard" _.defaultsDeep like this (eg. like merge-defaults):
This is now crashing with
RangeError: Maximum call stack size exceeded
:Somehow the
_.merge
gets stuck on merging the{
char, Haven't found something that could explain this by reading the changelog yet.Worked in the v2.4 branch.
The text was updated successfully, but these errors were encountered: