© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I would like to add that I've experimented with this a lot and it appears to be the combination of visiting a site that uses transparent PNGs stacked on top of each other with CSS while not have 3D graphics card acceleration. Many Linux users do not have 3D graphics card acceleration due to the fact that closed-source graphics drivers are not installed by default (and the open-source graphics drivers capable of 3D acceleration are either alpha quality or do not support all cards).
The point is, this bug is not specific to only Linux users. However, Linux users are much more likely to experience the problem due to the current graphics drivers situation.
Basically the work of interpreting two or more stacked alpha channels is being pushed onto the processor rather than the graphics card, essentially maxing the proc out and bringing the entire system to a halt. I've experienced a 100% CPU usage just scrolling up and down on http://
Proposed solutions:
A) have an option within about:config to toggle off the display of transparent PNGs (this is only a temporary fix for those who even know what "about:config" is). An extension could be developed as well, but again, this is a poor solution. Not everyone knows what an extension is, nor do they actually know why web pages appear to be slow after installing Linux on their computer.
B) rethink the way Fx renders stacked transparent PNGs
C) detect when a user does not have 3D acceleration. If it is determined that no acceleration is present, then handle transparent PNGs differently
Obviously (C) looks like the best choice. This is a VERY serious bug, and as such should have top priority. Fx cannot leave Linux users in the dust. This includes future One Laptop Per Child users, who will have no 3D acceleration whatsoever.
test pages:
http://
http://