Issue metadata
Sign in to add a comment
|
Remote tracing doesn't work |
||||||||||||||||||||||
Issue descriptionFollow the instructions to remotely trace Chrome on an Android device: https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs In chrome://inspect?tracing page, click the trace link beside the title of Chrome on device. See chrome://tracing window opened, but there is no "This about:tracing is connected to a remote device..." yellow bar. Click "Record" and start tracing and stop tracing. See traces collected from the host Chrome, not from the remote device.
,
Jan 11 2017
,
Jan 12 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/3a06f2645235a7de84376c6615553957e49d0563 commit 3a06f2645235a7de84376c6615553957e49d0563 Author: caseq <caseq@chromium.org> Date: Thu Jan 12 02:31:39 2017 Fix remote trace recording via chrome://inspect?tracing This was regressed in two different places, first by https://codereview.chromium.org/2515903002 and then by https://codereview.chromium.org/2607833002 BUG= 680170 Review-Url: https://codereview.chromium.org/2628863003 Cr-Commit-Position: refs/heads/master@{#443121} [modify] https://crrev.com/3a06f2645235a7de84376c6615553957e49d0563/chrome/browser/devtools/devtools_ui_bindings.cc
,
Jan 17 2017
,
Mar 9 2017
Issue 699808 has been merged into this issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by wangxianzhu@chromium.org
, Jan 11 2017Owner: caseq@chromium.org
Status: Assigned (was: Untriaged)