Version: ToT
OS: Android
What steps will reproduce the problem?
(1) build/android/adb_chrome_public_command_line --trace-startup='-*,disabled-by-default-memory-infra' --trace-startup-file=/sdcard/Download/trace.json --trace-startup-duration=40 --enable-low-end-device-mode
(2) Kill chromium if it is alive
(3) adb shell am start -a android.intent.action.VIEW http://edition.cnn.com
(4) Wait for 40+ seconds
(5) adb pull /sdcard/Download/trace.json
Attached a trace. It seems that Oilpan consumes +70MB even on low-end device mode (I took this trace on my Nexus 5; it's difficult to take tracing on low-end devices because tracing overhead causes OOM). I'm not sure this is a real problem (maybe CNN is just too heavy) but I think it's worth investigating. I haven't checked how many times Oilpan ran GCs but I'm sure there are plenty idle time.
haraken-san, keishi-san, could you take a look?
|
Deleted:
trace.json.gz
4.5 MB
|
Comment 1 by haraken@chromium.org
, Apr 5 2016