From bb5f0606912e535b6db4c82f2c33e9e24a18cd33 Mon Sep 17 00:00:00 2001 From: T-O-R-U-S Date: Mon, 14 Feb 2022 19:01:06 +0400 Subject: [PATCH] doc: fixed naming convention and made stylistic change --- ...tive_memory_leak.md => investigating-native-memory-leak.md} | 3 +++ 1 file changed, 3 insertions(+) rename doc/contributing/{investigating_native_memory_leak.md => investigating-native-memory-leak.md} (99%) diff --git a/doc/contributing/investigating_native_memory_leak.md b/doc/contributing/investigating-native-memory-leak.md similarity index 99% rename from doc/contributing/investigating_native_memory_leak.md rename to doc/contributing/investigating-native-memory-leak.md index fba03a1ed9a7cf..667c5a8355afbc 100644 --- a/doc/contributing/investigating_native_memory_leak.md +++ b/doc/contributing/investigating-native-memory-leak.md @@ -450,3 +450,6 @@ Running Valgrind using the debug build of Node.js shows: Now we can see the specific file name and line in the Node.js code which caused the allocation (inspector\_agent.cc:140). + +Thusly, we can examine the line (and its surrounding code) in order +to find a potential solution for the memory leak.