tree: 07038e21516a323262972cc680142eaf4e4fd621 [path history] [tgz]
  1. shared_ring_buffer_fuzzer_corpus/
  2. bookkeeping.cc
  3. bookkeeping.h
  4. bookkeeping_unittest.cc
  5. BUILD.gn
  6. client.cc
  7. client.h
  8. client_unittest.cc
  9. heapprofd_end_to_end_test.cc
  10. heapprofd_producer.cc
  11. heapprofd_producer.h
  12. interner.h
  13. interner_unittest.cc
  14. main.cc
  15. malloc_hooks.cc
  16. proc_utils.cc
  17. proc_utils.h
  18. proc_utils_unittest.cc
  19. README.md
  20. sampler.h
  21. sampler_unittest.cc
  22. scoped_spinlock.cc
  23. scoped_spinlock.h
  24. shared_ring_buffer.cc
  25. shared_ring_buffer.h
  26. shared_ring_buffer_fuzzer.cc
  27. shared_ring_buffer_unittest.cc
  28. system_property.cc
  29. system_property.h
  30. system_property_unittest.cc
  31. unwinding.cc
  32. unwinding.h
  33. unwinding_fuzzer.cc
  34. unwinding_unittest.cc
  35. unwound_messages.h
  36. wire_protocol.cc
  37. wire_protocol.h
  38. wire_protocol_unittest.cc
src/profiling/memory/README.md

heapprofd - Android Heap Profiler

Googlers, for design doc see: http://go/heapprofd-design

heapprofd requires Android Q.

Using convenience script

Use the tools/heap_profile script to heap profile a process. If you are having trouble make sure you are using the latest version.

See all the arguments using tools/heap_profile -h, or use the defaults and just profile a process (e.g. system_server):

tools/heap_profile --name system_server

This will create a heap dump when Ctrl+C is pressed.

The resulting profile proto contains four views on the data

  • space: how many bytes were allocated but not freed at this callstack the moment the dump was created.
  • alloc_space: how many bytes were allocated (including ones freed at the moment of the dump) at this callstack
  • objects: how many allocations without matching frees were done at this callstack.
  • alloc_objects: how many allocations (including ones with matching frees) were done at this callstack.

Googlers: Head to http://pprof/ and upload the gzipped protos to get a visualization.

Speedscope can also be used to visualize the heap dump, but will only show the space view.

Manual

To start profiling the process ${PID}, run the following sequence of commands. Adjust the INTERVAL to trade-off runtime impact for higher accuracy of the results. If INTERVAL=1, every allocation is sampled for maximum accuracy. Otherwise, a sample is taken every INTERVAL bytes on average.

INTERVAL=128000

adb shell su root setenforce 0
adb shell su root start heapprofd

echo '
buffers {
  size_kb: 100024
}

data_sources {
  config {
    name: "android.heapprofd"
    target_buffer: 0
    heapprofd_config {
      sampling_interval_bytes: '${INTERVAL}'
      pid: '${PID}'
      continuous_dump_config {
        dump_phase_ms: 10000
        dump_interval_ms: 1000
      }
    }
  }
}

duration_ms: 20000
' | adb shell perfetto --txt -c - -o /data/misc/perfetto-traces/trace

adb pull /data/misc/perfetto-traces/trace /tmp/trace

While we work on UI support, you can convert the trace into pprof compatible heap dumps. To do so, run

prodaccess
/google/bin/users/fmayer/third_party/perfetto:trace_to_text_sig/trace_to_text \
profile /tmp/trace

This will create a directory in /tmp/ containing the heap dumps. Run

gzip /tmp/heap_profile-XXXXXX/*.pb

to get gzipped protos, which tools handling pprof profile protos expect. Head to http://pprof/ and upload the gzipped protos to get a visualization.