Comments (7)
Sounds like you're probably using a synchronous function. With an async function, this won't happen.
from async.
I need the synchronous version...
from async.
That would be Array.prototype.map in modern browsers. You might want to look at underscore.js if you need support for older versions.
from async.
First I am coding in server side (Node).
Second I need mapSeries (each iterator in series!)
The problem appear only with large array (over ~3500 items)...
from async.
For example :
async.mapSeries(
arr,
function (item, callback) {
// Action taking server ressource and a bit of time...
// Then when finish call the callback for next item...
},
function (err, results) {
// ...
}
});
If my collection have less than 3000 items everything work fine but over a certain limit (~3500) not anymore...
from async.
try process.nextTick(callback)
, but usual Array.prototype.map
should be enough for synchronous map in nodejs
from async.
Same problem here, I am not using sync functions in mapSeries, and bobrik's suggestion does not solve it.
from async.
Related Issues (20)
- reflect does not use Error message HOT 1
- Enable OpenSSF Scorecard Github Action and Badge
- How to call functions to execute sequentially? HOT 1
- async package should distribute both cjs and esm HOT 1
- Add adaptive functions HOT 1
- with async.queue order of execution is different when using promises instead of callbacks but should be identical HOT 2
- How to figure version of async required? HOT 1
- Async causing issues with callback function HOT 2
- callback is not a function HOT 3
- Java
- Github
- Vulnerability in the async dependency HOT 1
- vulnerability in async module HOT 2
- Error propagation - Original error lost HOT 4
- How to reproduce Subtle Memory Leak? HOT 3
- async.each/async.eachSeries does not work properly when there is another async.each/eachSeries inside the callback HOT 2
- Is there a way to empty the queue workersList items?
- Is there any way to limit the size of the async.queue? HOT 3
- Mixing native async and Node callback functions seems to cause unexpected behavior HOT 2
- async.eachSeries with TypeScript gets stuck on first element in the collection HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from async.