Bug 66970
| Summary: | [chromium] Move render_widget scheduler into CCLayerTreeHostImplMainThreadProxy | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Nat Duca <nduca> |
| Component: | WebCore Misc. | Assignee: | Nat Duca <nduca> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | wbaxter |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 66807 | ||
| Bug Blocks: | 66922 | ||
Nat Duca
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |