Home | History | Annotate | only in /external/chromium_org/tools/memory_watcher
Up to higher level directory
NameDateSize
call_stack.cc11-Dec-201313.4K
call_stack.h11-Dec-20135.3K
DEPS11-Dec-201347
dllmain.cc11-Dec-20134.5K
hotkey.h11-Dec-20131.2K
ia32_modrm_map.cc11-Dec-20133.6K
ia32_opcode_map.cc11-Dec-2013106.5K
memory_hook.cc11-Dec-201319.2K
memory_hook.h11-Dec-20134.4K
memory_watcher.cc11-Dec-20137.5K
memory_watcher.gyp11-Dec-20131.2K
memory_watcher.h11-Dec-20132.7K
mini_disassembler.cc11-Dec-201313.8K
mini_disassembler.h11-Dec-20136.2K
mini_disassembler_types.h11-Dec-20136.5K
preamble_patcher.cc11-Dec-20139.6K
preamble_patcher.h11-Dec-201312.3K
preamble_patcher_with_stub.cc11-Dec-20137.4K
README11-Dec-2013721
scripts/11-Dec-2013

README

      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.
     18