From e4c3bc3780b2f61f2bdee573eb8aaae90ced9a54 Mon Sep 17 00:00:00 2001 From: Aarti Verma <75892381+vermaaarti@users.noreply.github.com> Date: Wed, 12 Oct 2022 03:20:32 +0530 Subject: [PATCH] Added content on memory leaks, its causes and its detectors (#2342) * Added content on memory leaks, its causes and its detectors also added some free blog links for more information * Update content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/100-memory-leaks/readme.md Co-authored-by: Kamran Ahmed --- .../116-nodejs-more-debugging/100-memory-leaks/readme.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/100-memory-leaks/readme.md b/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/100-memory-leaks/readme.md index 21bbaaae6..56a966cc8 100644 --- a/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/100-memory-leaks/readme.md +++ b/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/100-memory-leaks/readme.md @@ -1 +1,8 @@ -# Memory leaks \ No newline at end of file +# Memory Leaks + +Memory leaks are caused when your Node.js app’s CPU and memory usage increases over time for no apparent reason. In simple terms, a Node.js memory leak is an orphan block of memory on the Heap that is no longer used by your app because it has not been released by the garbage collector. It’s a useless block of memory. These blocks can grow over time and lead to your app crashing because it runs out of memory. + +Free Content +Memory leaks in Node.js +Memory leaks causes +Memory leaks detectors