1 Answer
- Newest
- Most votes
- Most comments
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.
answered 8 months ago
Relevant content
- asked 3 years ago
- asked 3 years ago
- asked 7 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
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