Add controllerTraceDataKey to trace data |
||||
Issue descriptionWe need to add controller_trace_data_key to specify which trace data come from the tracing controller. See: https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/edit#heading=h.q8di1j2nawlp
,
Mar 1 2016
Oystein, is there a way to distinguish if tracing is initialized by Chrome as the controller? Can I assume the StringTraceDataSink and CompressedStringTraceDataSink in tracing_controller_impl_data_sinks are always used by Chrome as the controller? Or should I instead set controller_trace_data_key in tracing_ui? That is: https://code.google.com/p/chromium/codesearch#chromium/src/content/browser/tracing/tracing_ui.cc&l=192 (right before calling stop tracing) Does this cover both chrome://tracing and chrome://inspect?tracing? By the way, I just realized that maybe I should use controllerTraceDataKey instead of controller_trace_data_key?
,
Mar 1 2016
,
Mar 28 2016
This is probably not needed on the Chrome side.
,
Feb 2 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by zh...@chromium.org
, Feb 29 2016