New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 2 users
Status: Fixed
User never visited
Closed: Sep 2012
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Sign in to add a comment
Ammo.js example runs much slower in recent dev channel
Reported by, May 15 2012 Back to list
Chrome Version       : 20.0.1132.3
OS Version: 6.0 (Windows Vista, Windows Server 2008)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
  Firefox 12.0: OK
Firefox 15.0a1 (2012-05-15) : OK

What steps will reproduce the problem?
1. Run the test at the above URL.

What is the expected result?
Smooth framerate like in FF and older versions of Chrome.

What happens instead?
Stuttering and poor framerate for the first run of the test.

Please provide any additional information below. Attach a screenshot if

UserAgentString: Mozilla/5.0 (Windows NT 6.0; WOW64) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.3 Safari/536.11

Comment 1 by, May 17 2012
Labels: -Area-Undefined -OS-Windows Area-Internals OS-All Feature-GPU-WebGL
Status: Assigned
Some preliminary investigation has been done and V8 bug has been filed about this. The basic problem (long compilation times) doesn't look like a recent regression, if it's a regression at all, but it looks like multiple recent changes have compounded the problem and now startup of Emscripten-compiled code performs really poorly.

Assigning to danno; perhaps dupe this bug to the V8 bug.

Note also that  Issue 123822  describes a similar problem with long compilation times.

Comment 2 by, May 31 2012
Comment 3 by, Sep 26 2012
Status: Fixed
Fixed in v8:r12613.
Project Member Comment 4 by, Mar 10 2013
Labels: -Area-Internals -Feature-GPU-WebGL Cr-Internals-GPU-WebGL Cr-Internals
Project Member Comment 5 by, Apr 10 2013
Labels: -Cr-Internals-GPU-WebGL Cr-Blink-WebGL
Sign in to add a comment