Bug 66970 - [chromium] Move render_widget scheduler into CCLayerTreeHostImplMainThreadProxy
Summary: [chromium] Move render_widget scheduler into CCLayerTreeHostImplMainThreadProxy
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nat Duca
URL:
Keywords:
Depends on: 66807
Blocks: 66922
  Show dependency tree / graph
 
Reported: 2011-08-25 11:55 PDT by Nat Duca
Modified: 2013-04-08 11:22 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nat Duca 2011-08-25 11:55:58 PDT 
Currently, when accelerated compositing is on, scheduling is done by the render widget if !USE(THREADED_COMPOSITING), and by the mainthreadproxy if USE(THREADED_COMPOSITING) and !CCSettings.enableThread.

To remove this mess, we need to implement some sort of renderer scheduling algorithm on the CCLayerTreeHostImplProxy so that we can end-of-life the render_widget's compositing scheduler.