Summary: | [chromium] Gracefully handle compositor initialization failure in single-threaded proxy | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | James Robinson <jamesr> | ||||||
Component: | New Bugs | Assignee: | James Robinson <jamesr> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | cc-bugs, enne, kbr, vangelis, webkit.review.bot | ||||||
Priority: | P2 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Attachments: |
|
Description
James Robinson
2012-02-07 11:54:33 PST
Created attachment 125894 [details]
Patch
Created attachment 125908 [details]
Patch
Fixed the threaded case too Comment on attachment 125908 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=125908&action=review Looks OK assuming it's been tested; one comment. > Source/WebCore/platform/graphics/chromium/cc/CCLayerTreeHost.h:187 > + bool updateLayers(); Please document the semantics of the return value. Why do some of the early outs in updateLayers return true? Committed r106986: <http://trac.webkit.org/changeset/106986> |