1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Inspect your Node.js application for memory leaks. Even if you increase the memory limit, a memory leak can eventually lead to crashes and use memory profiling tools to understand how your application is using memory and identify potential areas for optimization.
répondu il y a 4 mois
Contenus pertinents
- demandé il y a un an
- demandé il y a 8 mois
- demandé il y a 2 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
Thank you for looking into this. I've created a test script that recreates the problem. There are no leaks (unless in V8). I intentionally use more than 16GB of memory inside the test script. It runs fine on a local machine under MacOS and fails on AWS as soon as 16GB is reached