1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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.
beantwortet vor 3 Monaten
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
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