Stop using the TRACE_EVENT_*_ETW macros.

content/browser/browser_main.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "content/browser/browser_main.h"
 
 #include "base/trace_event/trace_event.h"
 #include "content/common/content_constants_internal.h"
 #include "content/public/browser/browser_main_runner.h"
 
 namespace content {
 
 // Main routine for running as the Browser process.
 int BrowserMain(const MainFunctionParams& parameters) {
-  TRACE_EVENT_BEGIN_ETW("BrowserMain", 0, "");
+  // Don't use the TRACE_EVENT0 macro because the tracing infrastructure doesn't
+  // expect synchronous events around the main loop of a thread.
+  TRACE_EVENT_ASYNC_BEGIN0("startup", "BrowserMain", 0);
+
   base::trace_event::TraceLog::GetInstance()->SetProcessName("Browser");
   base::trace_event::TraceLog::GetInstance()->SetProcessSortIndex(
       kTraceEventBrowserProcessSortIndex);
 
   scoped_ptr<BrowserMainRunner> main_runner(BrowserMainRunner::Create());
 
   int exit_code = main_runner->Initialize(parameters);
   if (exit_code >= 0)
     return exit_code;
 
   exit_code = main_runner->Run();
 
   main_runner->Shutdown();
 
-  TRACE_EVENT_END_ETW("BrowserMain", 0, 0);
+  TRACE_EVENT_ASYNC_END0("startup", "BrowserMain", 0);

[beaudoin, 2015/10/06 20:57:38]

There's a "return" a couple of lines above that will "leak" this async event. I
get it was like that before but maybe we should fix it now?

[brucedawson, 2015/10/07 00:42:56]

Seems worth fixing.

[fdoray, 2015/10/07 15:46:49]

Done.

 
   return exit_code;
 }
 
 }  // namespace content