Closed Bug 589867 Opened 14 years ago Closed 1 year ago

Xorg use 100% cpu while runing HTML5 game in FireFox4b3

Categories

(Core :: Graphics, defect)

x86_64
Linux
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mmichal_90, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0b3) Gecko/20100805 SUSE/4.0b-4.1 Firefox/4.0b3
Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b3) Gecko/20100805 SUSE/4.0b-4.1 Firefox/4.0b3

When i go to http://www.kevs3d.co.uk/dev/asteroids/
and i start play my xorg go crazy and use 100% of cpu (top show it). so i don't know what is wrong, sorry. I thing it's some thing with rendering because when i switch o retro mode (press "R"). It go well (until i add to much asteroids :P). I heard about FF use hardware but i don't see it in this case :/.



Reproducible: Always

Steps to Reproduce:
1.go to http://www.kevs3d.co.uk/dev/asteroids/
2.start play 



If it can help i use suse 11.3 gnome 2.30 xorg 1.8.0 
If you wand to say that i have slow machine pleas first check VPCF11S1E
Sounds like you have a slow graphics driver....  Have you reported this to your distribution?
Component: General → Graphics
QA Contact: general → thebes
No i don't raptor it, first i wand to know if it is slow graphics driver :P  i  run it in chrome it work well (14% of xorg). so i thing it can  be some thing with FF. I have nvidia driver 256.35. form repo. is it slow driver ??
Well, the driver is taking all the time.  So either it's happening to do something dumb for some operation we use and chrome doesn't (e.g. because chrome is just doing things itself instead of offloading work to the graphics driver) or we're asking it to do too much.

The former is much more likely given the state of graphics drivers on Linux; I strongly suggest reporting this to your distribution to see what they discover on their end too.
Severity: normal → S3

Unable to reproduce in current versions.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.