From 370de8163c52157881fdb656ca3582bc0699f6fe Mon Sep 17 00:00:00 2001 From: skieurfoufou <92753283+skieurfoufou@users.noreply.github.com> Date: Sun, 18 Sep 2022 13:31:00 +0300 Subject: [PATCH] Add memory management content (#1750) * Update readme.md * Update content/roadmaps/106-javascript/content/116-javascript-memory-management/readme.md Co-authored-by: Kamran Ahmed --- .../content/116-javascript-memory-management/readme.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/roadmaps/106-javascript/content/116-javascript-memory-management/readme.md b/content/roadmaps/106-javascript/content/116-javascript-memory-management/readme.md index 8b7c4ac50..f00cf5846 100644 --- a/content/roadmaps/106-javascript/content/116-javascript-memory-management/readme.md +++ b/content/roadmaps/106-javascript/content/116-javascript-memory-management/readme.md @@ -1 +1,6 @@ -# Javascript memory management \ No newline at end of file +# Memory Management + +Low-level languages like C, have manual memory management primitives such as malloc() and free(). In contrast, JavaScript automatically allocates memory when objects are created and frees it when they are not used anymore (garbage collection). This automaticity is a potential source of confusion: it can give developers the false impression that they don't need to worry about memory management. + +JavaScript Garbage Collection +Memory Management in JavaScript