Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(955)

Unified Diff: content/browser/browser_main_loop.cc

Issue 1386193002: Stop using the TRACE_EVENT_*_ETW macros. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 5 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: content/browser/browser_main_loop.cc
diff --git a/content/browser/browser_main_loop.cc b/content/browser/browser_main_loop.cc
index a4e2c8a189e0285ecba96dc35c8c4874aef7e0e4..5aa05675e33cc87f5f3aa5705f246d69faaae1c6 100644
--- a/content/browser/browser_main_loop.cc
+++ b/content/browser/browser_main_loop.cc
@@ -905,7 +905,9 @@ int BrowserMainLoop::PreMainMessageLoopRun() {
}
void BrowserMainLoop::RunMainMessageLoopParts() {
- TRACE_EVENT_BEGIN_ETW("BrowserMain:MESSAGE_LOOP", 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("toplevel", "BrowserMain:MESSAGE_LOOP", this);
bool ran_main_loop = false;
if (parts_)
@@ -914,7 +916,7 @@ void BrowserMainLoop::RunMainMessageLoopParts() {
if (!ran_main_loop)
MainMessageLoopRun();
- TRACE_EVENT_END_ETW("BrowserMain:MESSAGE_LOOP", 0, "");
+ TRACE_EVENT_ASYNC_END0("toplevel", "BrowserMain:MESSAGE_LOOP", this);
}
void BrowserMainLoop::ShutdownThreadsAndCleanUp() {

Powered by Google App Engine
This is Rietveld 408576698