-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
detectSeries breaks when iterating over large arrays #1293
Labels
Comments
This is a bug in the handler of the case of a resolved #1064 would fix this |
Is there a more short term fix that doesn't involve #1064? This seems pretty major - surprised it didn't pop up sooner. |
Not sure, thinking maybe an internal only #1064 is called for though |
Given that the issue is caused by the callback essentially being replaced
with function(cb) { cb(); } it strikes me a quick fix is to instead replace
it with function(cb) { setImmediate(cb); }.
|
megawac
added a commit
that referenced
this issue
Oct 15, 2016
megawac
added a commit
that referenced
this issue
Oct 15, 2016
suguru03
added a commit
to suguru03/neo-async
that referenced
this issue
Oct 16, 2016
hargasinski
pushed a commit
to hargasinski/async
that referenced
this issue
Nov 1, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Async 2.0.1, Node v0.10.29.
detectSeries on a large array causes a stack overflow even if the callbacks are called via setImmediate. Test case:
What did you expect to happen?
What was the actual result?
The bug appears to be tied to the size of arr. arr with 1000 items does not trigger the issue on my system.
The text was updated successfully, but these errors were encountered: