Removed requirement for the renderer to know it's process ID

ui/events/latency_info.h

 // Copyright 2013 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.
 
 #ifndef UI_EVENTS_LATENCY_INFO_H_
 #define UI_EVENTS_LATENCY_INFO_H_
 
 #include <map>
 #include <utility>
 
 #include "base/basictypes.h"
+#include "base/process/process_handle.h"
 #include "base/time/time.h"
 #include "ui/events/events_base_export.h"
 
 namespace ui {
 
 enum LatencyComponentType {
   // ---------------------------BEGIN COMPONENT-------------------------------
   // BEGIN COMPONENT is when we show the latency begin in chrome://tracing.
   // Timestamp when the input event is sent from RenderWidgetHost to renderer.
   INPUT_EVENT_LATENCY_BEGIN_RWH_COMPONENT,
@@ skipping 94 matching lines @@
                    int64 id,
                    LatencyComponent* output) const;
 
   void RemoveLatency(LatencyComponentType type);
 
   void Clear();
 
   // Records the |event_type| in trace buffer as TRACE_EVENT_ASYNC_STEP.
   void TraceEventType(const char* event_type);
 
+  static void AnnotateWithProcessId(std::vector<ui::LatencyInfo>& latency_info,
+                                    base::ProcessId process_id);

[jamesr, 2014/01/16 23:07:21]

nit: i don't think that the ID used here is actually a PID

+
+  // Some LatencyComponents generated in the renderer, specifically
+  // WINDOW_SNAPSHOT_FRAME_NUMBER_COMPONENTs, require a ProcessId to route
+  // notifications correctly. Since that cannot be given in the renderer
+  // this function patches the ProcessId in from the browser process.
+  void AnnotateComponentsWithProcessId(base::ProcessId process_id);
+
   LatencyMap latency_components;
   // The unique id for matching the ASYNC_BEGIN/END trace event.
   int64 trace_id;
   // Whether a terminal component has been added.
   bool terminated;
 };
 
 }  // namespace ui
 
 #endif  // UI_EVENTS_LATENCY_INFO_H_