Re: [chromium-dev] GPU Profiler Traces not showing in Chrome-Beta for Android

135 views
Skip to first unread message

Tom Hudson

unread,
Dec 13, 2013, 6:24:01 AM12/13/13
to Sohan Jyoti Ghosh, Chromium-dev
I'm not entirely certain what your problem is.

One possibility, which I think is suggested by "data is there in the trace file, but it is unable to display": the json format for traces frequently has incompatible changes. You'll want to make sure you're loading the trace into a desktop Chrome (or TraceViewer) that is the same version as the version of Chrome for Android you took the trace with. Newer versions of Chrome/TraceViewer usually work, but not always. So grab a Canary or tip-of-tree build and see if you can load the trace there.

Open the Javascript console and see if there are any error messages? It's possible to corrupt your trace by, say, adding non-ASCII characters to a TRACE_EVENT that break JSON parsing, or failing to handle lifetimes of temporary strings properly and embedding random garbage into the files.

Another possibility: it's not clear from that command line what categories you're tracing.


On Fri, Dec 13, 2013 at 8:25 AM, Sohan Jyoti Ghosh <sohan...@samsung.com> wrote:
Hello,

We are not able to get trace diagram for latest beta or trunk code content shell for Android,
Data is there in the trace file, but it is unable to display.

Chrome Beta Version - 32.0.1700.58

Command Used: adb shell am broadcast -a com.chrome.beta.GPU_PROFILER_START -e file /sdcard/Download/trace.txt 

Can anyone give some input to fix it.

Thanks,
Sohan

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

Sami Kyostila

unread,
Dec 13, 2013, 6:28:32 AM12/13/13
to Tom Hudson, Sohan Jyoti Ghosh, Chromium-dev
Hi Sohan,

It sounds like you're trying to load the trace file in an older version of Chrome like Tom already pointed out. I just wanted to mention that the build/android/adb_profile_chrome script is a more convenient way to record traces on Android. See http://dev.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs for instructions.

- Sami

Sohan Jyoti Ghosh

unread,
Dec 13, 2013, 7:12:08 AM12/13/13
to chromi...@chromium.org, Tom Hudson, Sohan Jyoti Ghosh
Thanks Tom and Sami,

I was indeed trying to load the trace in older chrome version.
But, as you pointed out, using ./build/android/adb_profile_chrome i am able to get the traces using old chrome as well.

I had to enable  --trace-cc, --trace-gpu though.

Thanks again,
Sohan

Sohan Jyoti Ghosh

unread,
Dec 13, 2013, 7:42:54 AM12/13/13
to chromi...@chromium.org, Sohan Jyoti Ghosh

Maybe I spoke too soon, the complete trace is still not available, Compositor/CompositorRasterWorker etc are still missing.
Looks like Browser Process is displayed, but the Render Process data isn't.

Thanks,
Sohan
Reply all
Reply to author
Forward
0 new messages