657371 - User report: After playing Chrome AngryBirds for a while, Firefox gets slower and slower until it crawls to a complete halt

Status: RESOLVED DUPLICATE of bug 678627

(Core :: JavaScript Engine, defect)

Description

[Marco Zehe (:MarcoZ)]

This was reported to me by a friend. I myself cannot play Angry Birds, so have no way to contribute for bug verification or lack thereof, I am just passing along the report.

After playing Angry Birds for Chrome for a while (see URL above) using Firefox 4.0., Firefox crawls to a halt, after continually becoming slower and slower while the game progresses.

At the end, there's no other way than to end the process through Windows Task manager and start a new Firefox session afterwards.

Comment 1

[AlsterNerd]

I reported this bug first to him, now I test it until i got all bugs i can get there.

Plattform is Ubuntu 11.04 Natty.
And after playing another while, after restart of Firefox, Javascript doesnt halt or break, but it doesn't display images relevant for the game.

Comment 2

[AlsterNerd]

While loading it later it has a big blue block in the images, that sometimes fades by moving it with the mouse, should be under the floor image.
Also it does blink.
And the fade in/fade out, with the mouse wheel doesn't work.

I know it's officially build for chrome, but fully javascript based and I think that it would be nice if it works in other browsers like FireFox too.

Comment 3

[AlsterNerd]

It seems that the issues improve with the level you reach within the game.
most issues now in level 3-10

Comment 4

[Justin Lebar (not reading bugmail)]

Does the issue arise with both the SD and HD versions?

Comment 5

[AlsterNerd]

It's within the canvas aka the SD Version.
In HD it gets slow faster than in the SD and crashes faster

Comment 6

[Boris Zbarsky [:bzbarsky]]

AlsterNerd, what does memory usage look like while this is going on?

Also, do you see the same behavior with a Nightly build?  What about Aurora?

Comment 7

[Justin Lebar (not reading bugmail)]

Both the SD and HD versions are broken for me on trunk -- only the background (and occasionally the slingshot) shows up.  If I manage to click in the right place I think I can shoot off a bird, because the screen scrolls appropriately...

Comment 8

[Boris Zbarsky [:bzbarsky]]

Sounds like bug 657403; should be fixed in tomorrow's nightlies.

Comment 9

[RNicoletto]

I played the first six levels of the game.
On Windows XP, with Firefox 4.0.1: 
[*] the HD version is slow and CPU intensive;
[*] the SD version is less slow (but not smooth) and CPU intensive.

On the same machine Chrome 11 is smooth and CPU intensive.

No crashes or hangs for me. My config ==> http://pastebin.com/qsyDuJtx

Comment 10

[Boris Zbarsky [:bzbarsky]]

So as far as I can tell at least on Mac the main issues here are painting, not JS...  But I can't reproduce the progressive slowdown, with a trunk build.  It's just always CPU intensive.

Comment 11

[Hugh Nougher [:Hughman]]

Observations with latest nightly.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0a1) Gecko/20110522 Firefox/6.0a1

Observation 1: In SD mode there is a sawtooth effect which does not appear to be anything more than lack of GC. Rise is about 100KB/sec while at "play" screen. Seems to be gc-heap + other although other goes negative after GC so its hard to see. Saw it rise to more than 280MB from starting point of 125MB, 170MB after GC. Likely bug 656120 related.

Observation 2: HD version uses more memory every time you reload the tab its in without dropping. All memory goes into mapped/other. Running GC, GC+CC, Closing tab do not help. Navigating away does free the memory. Memory rises by about 30-40MB every reload. Likely bug 637449 since I think this uses WebGL. Steps:
1. Load http://chrome.angrybirds.com/?version=hd
2. Let it get to the "Play" screen with music playing.
3. Press the reload button.
4. Repeat steps 2-3.

Observation 3: HD version uses less CPU than SD version on my machine. (YAY)
Observation 4: Music gets very annoying after a few hours. Good game though.

Comment 12

[AlsterNerd]

Maybe it's that Chrome on Version 10.x let the graphics card do some of the work.
That should explain the hugh CPU usage.
So it's very possible that its the WebGL thing

Comment 13

[AlsterNerd]

Oh, I forgot to post my UserAgentString:
Mozilla/5.0 (X11; Linux i686; rv:2.0.1) Gecko/20100101 Firefox/4.0.1

Comment 15

[Nicholas Nethercote [inactive]]

This is the same as bug 678627, that bug has more recent investigation (with newer versions of Firefox) so I'll dup this forward.