1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
# Startup Tracing with MemoryInfra
[MemoryInfra](README.md) supports startup tracing.
## The Simple Way
Start Chrome as follows:
$ chrome --no-sandbox \
--trace-startup=-*,disabled-by-default-memory-infra \
--trace-startup-file=/tmp/trace.json \
--trace-startup-duration=7
On Android, first ensure that Chrome can write output files to storage. Replace
"org.chromium.chrome" with the Chrome package you are tracing:
$ adb shell pm grant org.chromium.chrome android.permission.READ_EXTERNAL_STORAGE
$ adb shell pm grant org.chromium.chrome android.permission.WRITE_EXTERNAL_STORAGE
Then enable startup tracing and start Chrome as follows:
$ build/android/adb_chrome_public_command_line \
--trace-startup=-*,disabled-by-default-memory-infra \
--trace-startup-file=/sdcard/Download/trace.json \
--trace-startup-duration=7
$ build/android/adb_run_chrome_public
$ adb pull /sdcard/Download/trace.json # After tracing.
Note that startup tracing will be enabled upon every Chrome launch until you
delete the command-line flags:
$ build/android/adb_chrome_public_command_line ""
This will use the default configuration: one memory dump every 250 ms with a
detailed dump ever two seconds.
## The Advanced Way
If you need more control over the granularity of the memory dumps, you can
specify a custom trace config file as follows:
$ cat > /tmp/trace.config
{
"startup_duration": 4,
"result_file": "/tmp/trace.json",
"trace_config": {
"included_categories": ["disabled-by-default-memory-infra"],
"excluded_categories": ["*"],
"memory_dump_config": {
"triggers": [
{ "mode": "light", "periodic_interval_ms": 50 },
{ "mode": "detailed", "periodic_interval_ms": 1000 }
]
}
}
}
$ 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_run_chrome_public
$ adb pull /sdcard/Download/trace.json # After tracing.
Make sure that the "result_file" location is writable by the Chrome process on
Android (e.g. "/sdcard/Download/trace.json"). To ensure Chrome has permissions
to write to /sdcard, run the following, replacing "org.chromium.chrome" with
the Chrome package you are tracing:
$ adb shell pm grant org.chromium.chrome android.permission.READ_EXTERNAL_STORAGE
$ adb shell pm grant org.chromium.chrome android.permission.WRITE_EXTERNAL_STORAGE
Note that startup 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)
* [Memory tracing with MemoryInfra](README.md)
|
