Bug 59668 - [chromium] Compute compositor fps value and history using the frameBegin timestamp
Summary: [chromium] Compute compositor fps value and history using the frameBegin time...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Other OS X 10.5
: P2 Normal
Assignee: Nat Duca
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-27 20:19 PDT by Nat Duca
Modified: 2011-04-28 17:01 PDT (History)
6 users (show)

See Also:


Attachments
Patch (7.82 KB, patch)
2011-04-27 20:54 PDT, Nat Duca
no flags Details | Formatted Diff | Diff
Patch (7.15 KB, patch)
2011-04-28 10:00 PDT, Nat Duca
no flags Details | Formatted Diff | Diff
Patch (7.18 KB, patch)
2011-04-28 12:50 PDT, Nat Duca
no flags Details | Formatted Diff | Diff
chromiuuuuuuuuuuuuuuuuum ftw (7.17 KB, patch)
2011-04-28 14:10 PDT, Nat Duca
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Nat Duca 2011-04-27 20:19:12 PDT
[chromium] Compute compositor fps value and history using the frameBegin timestamp
Comment 1 Nat Duca 2011-04-27 20:54:26 PDT
Created attachment 91420 [details]
Patch
Comment 2 Eric Seidel (no email) 2011-04-28 02:02:47 PDT
Comment on attachment 91420 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=91420&action=review

> Source/WebCore/platform/graphics/chromium/LayerRendererChromium.cpp:58
> +using namespace WTF;

Generally wtf headers do this for you...

> Source/WebCore/platform/graphics/chromium/cc/CCHeadsUpDisplay.cpp:16
> + * DISCLAIMED. IN NO EVENT SHALL APPLE INC. OR ITS CONTRIBUTORS BE LIABLE FOR AYN

Nope.
Comment 3 Nat Duca 2011-04-28 10:00:51 PDT
Created attachment 91508 [details]
Patch
Comment 4 Darin Fisher (:fishd, Google) 2011-04-28 12:47:45 PDT
Comment on attachment 91508 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=91508&action=review

R=me, but please fix nits before committing.

> Source/WebCore/ChangeLog:9
> +        beginning of the frame rather than the time we call swapBuffers. When scheudling is

oops: scheudling

> Source/WebCore/platform/graphics/chromium/LayerRendererChromium.cpp:196
> +    // This value is currently inaccessible because it is up in RenderWidget.

I think you mean Chromium's RenderWidget (render_widget.cc), but this could be
confused with WebCore::RenderWidget.
Comment 5 Nat Duca 2011-04-28 12:50:54 PDT
Created attachment 91541 [details]
Patch
Comment 6 Darin Fisher (:fishd, Google) 2011-04-28 13:18:38 PDT
Comment on attachment 91541 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=91541&action=review

> Source/WebCore/platform/graphics/chromium/LayerRendererChromium.cpp:196
> +    // This value is currently inaccessible because it is up in Chromiuum's

Chromiuum -> Chromium
Comment 7 Nat Duca 2011-04-28 14:10:49 PDT
Created attachment 91551 [details]
chromiuuuuuuuuuuuuuuuuum ftw
Comment 8 WebKit Commit Bot 2011-04-28 16:50:06 PDT
Comment on attachment 91551 [details]
chromiuuuuuuuuuuuuuuuuum ftw

Clearing flags on attachment: 91551

Committed r85261: <http://trac.webkit.org/changeset/85261>
Comment 9 WebKit Commit Bot 2011-04-28 16:50:11 PDT
All reviewed patches have been landed.  Closing bug.
Comment 10 WebKit Review Bot 2011-04-28 17:01:42 PDT
http://trac.webkit.org/changeset/85261 might have broken WinCE Release (Build)