Skip to content

Valgrind_capitalization #41985

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mahmoud-moursy wants to merge 4 commits into from
Closed

Valgrind_capitalization #41985

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
b9231a6
Grammatical fixes + touch-ups to keep some docs inline with the guide
mahmoud-moursy Feb 14, 2022
bb5f060
doc: fixed naming convention and made stylistic change
mahmoud-moursy Feb 14, 2022
ca361f9
doc: reverted valgrind change & fixed lint errs
mahmoud-moursy Feb 15, 2022
d855d5a
Fixed Valgrind's capitalization in the docs
mahmoud-moursy Feb 15, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
doc: fixed naming convention and made stylistic change
  • Loading branch information
@mahmoud-moursy
mahmoud-moursy committed Feb 14, 2022
commit bb5f0606912e535b6db4c82f2c33e9e24a18cd33
3 changes: 3 additions & 0 deletions ...uting/investigating_native_memory_leak.md → ...uting/investigating-native-memory-leak.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.