Chrome Version: tip of tree
OS: linux

What steps will reproduce the problem?
(1) Add LOG(INFO) << "TracingStartedInPage"; to method InspectorTracingAgent::EmitMetadataEvents.
(2) Add LOG(INFO) << "Data" to method InspectorTracingStartedInFrame::Data;
(3) build and run chrome with --remote-debugging-port=9222
(4) run chrome-remote-interface inspect
  (4.1) Tracing.start({categories: '-*,disabled-by-default-devtools.timeline'})
  (4.2) Page.navigate({url: "http://www.example.com"})
  (4.3) Page.navigate({url: "https://www.google.com"})
  (4.4) Page.navigate({url: "http://www.github.com"})

What is the expected result?
In chrome runtime log, each "TracingStartedInPage" should be followed by a "Data", since the tracing category is enabled.

What happens instead?
Two TracingStartedInPage events are not recorded to trace.

[1:1:0128/165221.358613:INFO:InspectorTracingAgent.cpp(108)] TracingStartedInPage
[1:1:0128/165221.359089:INFO:InspectorTraceEvents.cpp(1260)] Data
[1:1:0128/165308.664600:INFO:InspectorTracingAgent.cpp(108)] TracingStartedInPage
[1:1:0128/165308.664964:INFO:InspectorTraceEvents.cpp(1260)] Data
[1:1:0128/165308.782149:ERROR:render_process_impl.cc(213)] WebFrame LEAKED 1 TIMES
[1:1:0128/165318.250968:INFO:InspectorTracingAgent.cpp(108)] TracingStartedInPage
[1:1:0128/165318.346268:ERROR:render_process_impl.cc(213)] WebFrame LEAKED 1 TIMES
[1:1:0128/165552.843633:INFO:InspectorTracingAgent.cpp(108)] TracingStartedInPage
[1:1:0128/165552.947121:ERROR:render_process_impl.cc(213)] WebFrame LEAKED 1 TIMES


Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.