[docs] Document MemoryInfra startup tracing on Android

components/tracing/docs/memory_infra_startup_tracing.md

Index: components/tracing/docs/memory_infra_startup_tracing.md
diff --git a/components/tracing/docs/memory_infra_startup_tracing.md b/components/tracing/docs/memory_infra_startup_tracing.md
index 02ac7ad132c529ff8890bbfbb30b0b7eb3379816..193b8b0b5b9855a311d667f2447eac471b3dcd31 100644
--- a/components/tracing/docs/memory_infra_startup_tracing.md
+++ b/components/tracing/docs/memory_infra_startup_tracing.md
@@ -11,6 +11,19 @@ Start Chrome as follows:
              --trace-startup-file=/tmp/trace.json \
              --trace-startup-duration=7
 
+On Android, enable startup tracing and start Chrome as follows:
+
+    $ build/android/adb_chrome_public_command_line \
+          --no-sandbox \

[Primiano Tucci (use gerrit), 2016/02/11 12:04:55]

no need of --no-sandbox on Android.
Let's keep the one above for a bit, until it makes to stable. IIRC on Android we
never really needed no-sanbox, was a linux thing only.

[petrcermak, 2016/02/11 12:20:49]

Done.

+          --trace-startup=-*,disabled-by-default-memory-infra \
+          --trace-startup-file=/storage/emulated/legacy/Download/trace.json \
+          --trace-startup-duration=7
+
+    $ build/android/adb_run_chrome_public  # Public.
+    $ clank/bin/adb_run_chrome             # Googlers only.

[Primiano Tucci (use gerrit), 2016/02/11 12:04:55]

hmm remove this, I imagine internal folks know how do run chrome.
Also because otherwise you need a copy also of the command line command above

+
+    $ adb pull /storage/emulated/legacy/Download/trace.json  # After tracing.

[Primiano Tucci (use gerrit), 2016/02/11 12:04:55]

I think that this should be aliased also via /sdcard/Download/trace.json, which
is easier to type and remember

[petrcermak, 2016/02/11 12:20:49]

Done (I wanted to mirror
https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/record...,
which mentions both).

+
 This will use the default configuration: one memory dump every 250 ms with a
 detailed dump ever two seconds.
 
@@ -37,6 +50,25 @@ specify a custom trace config file as follows:
 
     $ chrome --no-sandbox --trace-config-file=/tmp/trace.config
 
+On Android, the config file has to be pushed to a fixed file location:
+
+    $ adb root
+    $ adb push /tmp/trace.config /data/local/chrome-trace-config.json
+
+    $ build/android/adb_chrome_public_command_line --no-sandbox

[Primiano Tucci (use gerrit), 2016/02/11 12:04:55]

no need of --no-sandbox

[petrcermak, 2016/02/11 12:20:49]

Done.

+
+    $ build/android/adb_run_chrome_public  # Public.
+    $ clank/bin/adb_run_chrome             # Googlers only.

[Primiano Tucci (use gerrit), 2016/02/11 12:04:55]

ditto

[petrcermak, 2016/02/11 12:20:49]

Done (ditto).

+
+    $ adb pull /storage/emulated/legacy/Download/trace.json  # After tracing.
+
+Make sure that the "result_file" location is writable by the Chrome process on
+Android (e.g. "/storage/emulated/legacy/Download/trace.json"). Note that startup

[Primiano Tucci (use gerrit), 2016/02/11 12:04:55]

/sdcard

[petrcermak, 2016/02/11 12:20:49]

Done.

+tracing will be enabled upon every Chrome launch until you delete the config
+file:
+
+    $ adb shell rm /data/local/chrome-trace-config.json
+
 ## Related Pages
 
  * [General information about startup tracing](https://sites.google.com/a/chromium.org/dev/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs)