Bug 86539

Summary: [chromium] Contents flash when switching tabs when composting, due to drawing when content texture manager limit is 0.
Product: WebKit Reporter: Michal Mocny <mmocny>
Component: New BugsAssignee: Michal Mocny <mmocny>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: cc-bugs, danakj, jamesr, nduca, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Michal Mocny
Reported 2012-05-15 15:46:36 PDT
[chromium] Contents flash when switching tabs when composting, due to drawing when content texture manager limit is 0.
Attachments
Patch (2.92 KB, patch)
2012-05-15 15:49 PDT, Michal Mocny
no flags
Michal Mocny
Comment 1 2012-05-15 15:49:47 PDT
Michal Mocny
Comment 2 2012-05-15 15:54:49 PDT
Notes on the approach here: 1. We would prefer not to manually increase memory when a tab is foregrounded to get around the issue of drawing white frames, but this is a temporary solution until that larger problem is solved. Specifically, this is also happening without threaded compositor and it is unclear if https://bugs.webkit.org/show_bug.cgi?id=85108 fixes that, or if it will land soon. 2. Regarding early exit in setContentsMemoryAllocationLimitBytes, @danakj suggested we add a tag to the memory allocation struct saying "expected visibility". Then, we can early exit whenever the current state is != expected state, without specifically testing for bytes == 0.
Dana Jansens
Comment 3 2012-05-15 16:00:44 PDT
(In reply to comment #2) > Notes on the approach here: > > 1. We would prefer not to manually increase memory when a tab is foregrounded to get around the issue of drawing white frames, but this is a temporary solution until that larger problem is solved. Specifically, this is also happening without threaded compositor and it is unclear if https://bugs.webkit.org/show_bug.cgi?id=85108 fixes that, or if it will land soon. I *think* if we also make CCSingleThreadProxy skip drawing frames where prepareToDraw() fails, then bug #85108 would fix this problem. That could be done as a simple followup to 85108, or along with it.
Nat Duca
Comment 4 2012-05-15 22:56:03 PDT
agreed with dana
Michal Mocny
Comment 5 2012-05-22 08:08:18 PDT
*** This bug has been marked as a duplicate of bug 85108 ***
Adam Barth
Comment 6 2012-07-27 01:11:05 PDT
Comment on attachment 142085 [details] Patch Cleared review? from attachment 142085 [details] so that this bug does not appear in http://webkit.org/pending-review. If you would like this patch reviewed, please attach it to a new bug (or re-open this bug before marking it for review again).
Note You need to log in before you can comment on or make changes to this bug.