Bug 66743

Summary: [chromium] Remove obsolete child context list from LayerRendererChromium
Product: WebKit Reporter: James Robinson <jamesr>
Component: New BugsAssignee: James Robinson <jamesr>
Status: RESOLVED FIXED    
Severity: Normal CC: enne, jbates, kbr, vangelis, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 66435    
Attachments:
Description Flags
Patch none

James Robinson
Reported 2011-08-22 18:41:08 PDT
[chromium] Remove obsolete child context list from LayerRendererChromium
Attachments
Patch (10.78 KB, patch)
2011-08-22 18:43 PDT, James Robinson
no flags
James Robinson
Comment 1 2011-08-22 18:43:24 PDT
John Bates
Comment 2 2011-08-22 18:52:30 PDT
Comment on attachment 104781 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=104781&action=review My precious codez! > Source/WebCore/platform/graphics/chromium/LayerRendererChromium.cpp:-584 > - i->first->flush(); I think this was added during Al's flush patch. Not sure if it's necessary. Seems like it should be done elsewhere anyways.
James Robinson
Comment 3 2011-08-22 19:25:42 PDT
That was added to replace the latch that used to be there, but we don't need to explicit flushes here at all (see the ChangeLog).
James Robinson
Comment 4 2011-08-23 12:15:11 PDT
Comment on attachment 104781 [details] Patch Glad you like it, John, but I need a WebKit reviewer to r+ or the tools will yell at me. Ken, mind officially reviewing this?
Kenneth Russell
Comment 5 2011-08-23 13:58:25 PDT
Comment on attachment 104781 [details] Patch Looks good as long as it's been tested with various content to ensure that the flushes being removed aren't necessary.
WebKit Review Bot
Comment 6 2011-08-23 16:01:22 PDT
Comment on attachment 104781 [details] Patch Clearing flags on attachment: 104781 Committed r93647: <http://trac.webkit.org/changeset/93647>
WebKit Review Bot
Comment 7 2011-08-23 16:01:26 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.