Hello
I tracked down this problem to a stall in our ports rendering code when
it tries to send a message to our main app. Fixing the stall results in
a bubblemark score of 243, which is on par with the other browsers I
have on my system. Thanks for all of the suggestions.
Regards,
Rodney
On 06/29/2015 03:16 AM, Sergio Villar Senin wrote:
On 28/06/15 16:27, Rodney Dowdall wrote:
The only other question I have is if there is some sort of throttle on
the JavaScript callbacks. The reason I ask is because no matter what I
do, the following page:
http://bubblemark.com/dhtml.htm
I only get 60 fps. For this page the "fps" is a bit of misnomer because
they are just measuring the number of times they get a call in to their
JavaScript code. It doesn't seem to matter how many balls I draw on the
screen, I always get 60 fps .
Not completly sure about the mac port but I think it does the same as
gtk, i.e, they used that magic value of 60fps as a reference for the
accelerated compositor to know when to generate new frames.
BR
_______________________________________________
webkit-dev mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-dev
_______________________________________________
webkit-dev mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-dev
