chrome://inspect?tracing should show error from Chrome on Android |
||||||||
Issue descriptionIf something is wrong when tracing Chrome on Android remotely, there is no way to tell what goes wrong because chrome://inspect?tracing does not show any error from the remote device. One example is issue 576292 . So if there is a file on Android device: /data/local/chrome-trace-config.json, Chrome on Android will automatically start tracing when it is launched (startup tracing). Later, if you open chrome://inspect?tracing on the host machine and try to trace Chrome remotely (clicking "Record"), nothing happens (a dialog should have prompted which categories to enable). The problem is that when you try to trace remotely, you will get DevTools error: Tracing is already started. https://code.google.com/p/chromium/codesearch#chromium/src/content/browser/devtools/protocol/tracing_handler.cc&q=%22Tracing%20is%20already%20started%22 Such error is not transferred back to the host. So it is hard to figure out the problem.
,
Mar 30 2016
,
Jul 23 2016
Zhen, we actually send the error over the protocol, it's rather a matter of handling this error here: https://cs.chromium.org/chromium/src/third_party/catapult/tracing/tracing/ui/extras/about_tracing/inspector_tracing_controller_client.html?rcl=0&l=107
,
Oct 5 2016
,
Oct 5 2016
,
Feb 2 2017
,
Sep 21 2017
,
Dec 16 2017
,
Dec 17
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by zh...@chromium.org
, Mar 30 2016Owner: caseq@chromium.org
Status: Assigned (was: Untriaged)