WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
93734
[chromium] Remove targetSurface pointer from CCRenderPass
https://bugs.webkit.org/show_bug.cgi?id=93734
Summary
[chromium] Remove targetSurface pointer from CCRenderPass
Dana Jansens
Reported
2012-08-10 11:47:05 PDT
[chromium] Remove targetSurface pointer from CCRenderPass
Attachments
Patch
(13.64 KB, patch)
2012-08-10 11:49 PDT
,
Dana Jansens
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Dana Jansens
Comment 1
2012-08-10 11:49:25 PDT
Created
attachment 157782
[details]
Patch
Adrienne Walker
Comment 2
2012-08-10 11:56:09 PDT
Comment on
attachment 157782
[details]
Patch I suspect that this changed once the HUD became a layer, but are the debug rects now one frame behind?
Dana Jansens
Comment 3
2012-08-10 11:57:27 PDT
(In reply to
comment #2
)
> (From update of
attachment 157782
[details]
) > I suspect that this changed once the HUD became a layer, but are the debug rects now one frame behind?
Are you referring to the ordering change here? It seems that they would just never have any rects for surface damage, since it was being cleared just before it was being saved. Or are you referring to behaviour you're seeing in the HUD?
Adrienne Walker
Comment 4
2012-08-10 12:04:01 PDT
(In reply to
comment #3
)
> (In reply to
comment #2
) > > (From update of
attachment 157782
[details]
[details]) > > I suspect that this changed once the HUD became a layer, but are the debug rects now one frame behind? > > Are you referring to the ordering change here? It seems that they would just never have any rects for surface damage, since it was being cleared just before it was being saved. Or are you referring to behaviour you're seeing in the HUD?
Just trying to understand. It's a good thing the hud is so well-tested, sad trombone noise. This is what I understand from reading the code: Pre-HUD layer: debug rects saved, damage cleared, hud drawn Post-HUD layer: hud layer drawn, damage cleared, debug rects saved This patch: hud layer drawn, debug rects saved, damage cleared Or: Pre-HUD layer: debug rects for current frame drawn on current frame Post-HUD layer: debug rects for previous frame drawn on current frame, damage never drawn This patch: debug rects for previous frame drawn on current frame
Dana Jansens
Comment 5
2012-08-10 12:11:24 PDT
Oh I see. Here's what I see pre-HUD-layer: drawFrame drawHud clearDamage saveRects So, busted, and showing rects from the previous frame. Before this patch, I see: drawFrame (including Hud) clearDamage saveRects After this patch, I see: drawFrame (including Hud) saveRects clearDamage Maybe we should be saving rects before drawFrame, I'll open a bug and we can discuss with shawn.
Adrienne Walker
Comment 6
2012-08-10 12:13:36 PDT
Comment on
attachment 157782
[details]
Patch R=me. With respect to the HUD bug, this patch is still a strict improvement, so no reason not to land it.
WebKit Review Bot
Comment 7
2012-08-10 13:40:56 PDT
Comment on
attachment 157782
[details]
Patch Clearing flags on attachment: 157782 Committed
r125325
: <
http://trac.webkit.org/changeset/125325
>
WebKit Review Bot
Comment 8
2012-08-10 13:41:00 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.
Top of Page
Format For Printing
XML
Clone This Bug