Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(217)

Side by Side Diff: tools/memory_watcher/README

Issue 314253003: Remove memory_watcher tool as well as --memory-profile command line flag. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Fix compile issue on non-ChromeOS platforms Created 6 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « tools/memory_watcher/DEPS ('k') | tools/memory_watcher/call_stack.h » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(Empty)
1 memory_watcher is a library that can be linked into chromium to trace the
2 memory allocations. It works by hooking the system allocation/deallocation
3 functions, and recording the actions.
4
5 To use memory_watcher in chromium:
6
7 (1) Compile the memory_watcher library (it is part of the solution by default)
8
9 (2) Run chromium with these flags "--memory-profile -no-sandbox"
10 (The instrumentation doesn't work with the sandbox)
11
12 (3) Hit ctrl-alt-D to generate a dump of the memory allocations.
13 This will create a log file called memorywatcher.logXXXX for every
14 chromium process (where XXXX is the pid).
15
16 The log file is a human readable text format, which can be further analyzed
17 using the helpers in the "scripts/" directory.
OLDNEW
« no previous file with comments | « tools/memory_watcher/DEPS ('k') | tools/memory_watcher/call_stack.h » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698