Index: content/renderer/gpu/compositor_output_surface.cc |
diff --git a/content/renderer/gpu/compositor_output_surface.cc b/content/renderer/gpu/compositor_output_surface.cc |
index a240b19736e1d0ce8c85197b9b6102cbfe2e005a..b55ac2ae2e118416fd72d7347d0ec195dd7aa343 100644 |
--- a/content/renderer/gpu/compositor_output_surface.cc |
+++ b/content/renderer/gpu/compositor_output_surface.cc |
@@ -140,7 +140,6 @@ void CompositorOutputSurface::OnMessageReceived(const IPC::Message& message) { |
IPC_MESSAGE_HANDLER(ViewMsg_UpdateVSyncParameters, |
OnUpdateVSyncParametersFromBrowser); |
IPC_MESSAGE_HANDLER(ViewMsg_SwapCompositorFrameAck, OnSwapAck); |
- IPC_MESSAGE_HANDLER(ViewMsg_ReclaimCompositorResources, OnReclaimResources); |
IPC_END_MESSAGE_MAP() |
} |
@@ -165,16 +164,6 @@ void CompositorOutputSurface::OnSwapAck(uint32_t output_surface_id, |
client_->DidSwapBuffersComplete(); |
dcheng
2016/07/13 14:26:58
Does it matter that OnReclaimResources didn't call
Fady Samuel
2016/07/13 15:29:48
piman@ can better answer this question. I could ad
danakj
2016/07/13 18:40:20
This is what unthrottles the compositor to produce
|
} |
-void CompositorOutputSurface::OnReclaimResources( |
- uint32_t output_surface_id, |
- const cc::CompositorFrameAck& ack) { |
- // Ignore message if it's a stale one coming from a different output surface |
- // (e.g. after a lost context). |
- if (output_surface_id != output_surface_id_) |
- return; |
- ReclaimResources(&ack); |
-} |
- |
bool CompositorOutputSurface::Send(IPC::Message* message) { |
return message_sender_->Send(message); |
} |