[Webkit-unassigned] [Bug 116249] New: New Google Maps 3D is much choppier in r150183 than in Chrome 26.0.1410.65

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=116249

           Summary: New Google Maps 3D is much choppier in r150183 than in
                    Chrome 26.0.1410.65
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
               URL: http://www.google.com/maps/preview
        OS/Version: Unspecified
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebGL
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: bjhomer at gmail.com


Created an attachment (id=201994)
 --> (https://bugs.webkit.org/attachment.cgi?id=201994&action=review)
Webkit sample

The new Google Maps 3D view thing is pretty cool. But unfortunately, it's quite a bit slower in WebKit than in Chrome. You have to get an invitation, but they got mine to me the next day, so it wasn't too long a process.

When you go there, it will tell you that Safari isn't on its list of supported browsers, so you'll only get "Lite" mode. But I've got "Enable WebGL" checked in the Develop menu, so I did what they say (https://support.google.com/maps/bin/answer.py?hl=en&answer=3031966) and added ?force=webgl to the url. (i.e. http://www.google.com/maps/preview?force=webgl)

Steps to reproduce:
Once in the 3d maps thing, search for "New York City Battery Park" in the search field in the top left.
Click on "Earth" in the bottom left corner to switch to Earth mode instead of maps mode.
Zoom in until the buildings are nice and tall. Hold down Ctrl and drag your mouse to get some perspective.

Results:
At this point, it should start loading textures, and the CPU usage in the SafariForWebkitDevelopment process takes off. Things get pretty choppy for a while; 2-3 second response times for user interaction. Even after everything seems to have loaded, CPU usage stays at 30% or so. I've attached a sample, in case it's useful.

In contrast, when I do the same thing in Chrome, it's a little choppy, but not nearly as much. (Maybe 0.5 second response times at peak?) A "Google Chrome Renderer" process picks up for a while, but drops back down to 0.2% CPU after all the visible textures have loaded.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.