Chromium Code Reviews| Index: content/renderer/render_view_impl.cc |
| diff --git a/content/renderer/render_view_impl.cc b/content/renderer/render_view_impl.cc |
| index ecdd229fe586e4fab3cef684da039b8794e6704d..60b38250dff8b578de485f47cf4071e6a1d28824 100644 |
| --- a/content/renderer/render_view_impl.cc |
| +++ b/content/renderer/render_view_impl.cc |
| @@ -2757,9 +2757,10 @@ gfx::RectF RenderViewImpl::ClientRectToPhysicalWindowRect( |
| } |
| int64 RenderViewImpl::GetLatencyComponentId() { |
| - // Note: this must match the logic in RenderWidgetHostImpl. |
| - return GetRoutingID() | (static_cast<int64>( |
| - RenderThreadImpl::current()->renderer_process_id()) << 32); |
| + // The renderer is not allowed to know it's own process ID, so we use |
| + // kNullProcessId instead, which the browser process will later detect and |
| + // populate with the correct ID. |
| + return GetRoutingID() | (static_cast<int64>(base::kNullProcessId) << 32); |
|
jamesr
2014/01/16 23:07:21
why do we put the routing ID in here? I think the
|
| } |
| void RenderViewImpl::StartNavStateSyncTimerIfNecessary() { |