RendererCompositorFrameSink needs to directly get BeginFrames |
|||
Issue descriptionCurrently BeginFrame IPC messages go to CompositorExternalBeginFrameSource. Once RendererCompositorFrameSink is a MojoCompositorFrameSinkClient, it is going to get BeginFrames directly and it needs to be able to directly handle them.
,
Mar 24 2017
,
Mar 27 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/09812d36f72be34ba5e68441222750b4b0a6b3a9 commit 09812d36f72be34ba5e68441222750b4b0a6b3a9 Author: samans <samans@chromium.org> Date: Mon Mar 27 19:57:43 2017 RendererCompositorFrameSink should receive BeginFrame messages Currently, BeginFrame messsages are routed to CompositorExternalBeginFrameSource. Once we switch to MojoCompositorFrameSinkClient, we can't have ReclaimResources messages go to one class and BeginFrame messages go to another. RendererCompositorFrameSink must handle all BeginFrame-related messages. BUG= 704971 Review-Url: https://codereview.chromium.org/2773023002 Cr-Commit-Position: refs/heads/master@{#459859} [modify] https://crrev.com/09812d36f72be34ba5e68441222750b4b0a6b3a9/content/renderer/gpu/renderer_compositor_frame_sink.cc [modify] https://crrev.com/09812d36f72be34ba5e68441222750b4b0a6b3a9/content/renderer/gpu/renderer_compositor_frame_sink.h [modify] https://crrev.com/09812d36f72be34ba5e68441222750b4b0a6b3a9/content/renderer/render_thread_impl.cc [modify] https://crrev.com/09812d36f72be34ba5e68441222750b4b0a6b3a9/content/renderer/render_thread_impl.h
,
Oct 24 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by samans@chromium.org
, Mar 24 2017