Process names, and predictable thread and process ordering in about:tracing

content/gpu/gpu_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 <stdlib.h>
 
 #if defined(OS_WIN)
 #include <windows.h>
 #endif
 
@@ skipping 66 matching lines @@
   deferred_messages.Get().push(new GpuHostMsg_OnLogMessage(
       severity, header, message));
   return false;
 }
 
 }  // namespace anonymous
 
 // Main function for starting the Gpu process.
 int GpuMain(const MainFunctionParams& parameters) {
   TRACE_EVENT0("gpu", "GpuMain");
+  base::debug::TraceLog::GetInstance()->SetProcessLabel(0, "GPU Process");
+  base::debug::TraceLog::GetInstance()->SetProcessSortIndex(3);

[dsinclair, 2013/06/20 15:01:47]

Would it be useful to move some of these magic numbers into trace_event.h?

kGpuSortIndex, kBrowserSortIndex, etc? Keeps them major ones in one place so we
can easily see the sort order.

 
   const CommandLine& command_line = parameters.command_line;
   if (command_line.HasSwitch(switches::kGpuStartupDialog)) {
     ChildProcess::WaitForDebugger("Gpu");
   }
 
   base::Time start_time = base::Time::Now();
 
   bool in_browser_process = command_line.HasSwitch(switches::kSingleProcess) ||
                             command_line.HasSwitch(switches::kInProcessGPU);
@@ skipping 329 matching lines @@
     return true;
   }
 
   return false;
 }
 #endif  // defined(OS_WIN)
 
 }  // namespace.
 
 }  // namespace content