Implement profiler log writing at shutdown

chrome/common/chrome_switches.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 "chrome/common/chrome_switches.h"
 
 #include "base/base_switches.h"
 #include "base/command_line.h"
 
 namespace switches {
@@ skipping 965 matching lines @@
 
 // Specifies a location for profiling output. This will only work if chrome has
 // been built with the gyp variable profiling=1.
 //
 //   {pid} if present will be replaced by the pid of the process.
 //   {count} if present will be incremented each time a profile is generated
 //           for this process.
 // The default is chrome-profile-{pid}.
 const char kProfilingFile[]                 = "profiling-file";
 
+// Specifies a path to output profiling information at shutdown.

[jar (doing other things), 2012/02/08 20:34:37]

Please add to the comment to distinguish from the string on line 984.  Perhaps:

Specifies a path for the output of task-level-profiling, such as would can be
seen via about:profiler.

[rlarocque, 2012/02/08 23:49:44]

Done, with slightly different text.  I wanted to make it clear the output file
can be loaded into about:profiler.

+const char kProfilingOutputFile[]            = "profiling-output-file";
+
 // Controls whether profile data is periodically flushed to a file. Normally
 // the data gets written on exit but cases exist where chrome doesn't exit
 // cleanly (especially when using single-process). A time in seconds can be
 // specified.
 const char kProfilingFlush[]                = "profiling-flush";
 
 // Specifies a custom URL for fetching NTP promo data.
 const char kPromoServerURL[]                = "promo-server-url";
 
 // Forces proxy auto-detection.
@@ skipping 394 matching lines @@
 
 // -----------------------------------------------------------------------------
 // DO NOT ADD YOUR CRAP TO THE BOTTOM OF THIS FILE.
 //
 // You were going to just dump your switches here, weren't you? Instead, please
 // put them in alphabetical order above, or in order inside the appropriate
 // ifdef at the bottom. The order should match the header.
 // -----------------------------------------------------------------------------
 
 }  // namespace switches