Closed
Bug 778514
Opened 13 years ago
Closed 12 years ago
High CPU use on http://grssam.com/
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mayankleoboy1, Unassigned)
Details
Attachments
(1 file)
3.80 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0
Build ID: 20120728030524
Steps to reproduce:
opened the URL : http://waterfoxproject.org/
1. The page has an animation + some effects.
2.Monitor the CPU usage during the animation transition.
3. Monitor the CPU usage during scrolling on the page
4. Monitor CPU use during page idle.
Actual results:
CPU usages for Firefox :
Idle : 6%
animation : 15%
Scrolling : 23%
CPU usages for chrome/Opera
idle : 1%
animation: 2%
scrolling: 4%
Out of a possible 25% ( i have a quad core CPU)
All the animations/scrolling is smooth, so that is not the issue.
Expected results:
Idle and active CPU usage should have been lower.
Configuration :
win7 x64
core i3-350M
4GB RAM
ATI 5470M with 12.6 drivers.
Attaching the about:support info.
Cleopatra profile :
http://people.mozilla.com/~bgirard/cleopatra/?report=2e595de659941a4ad40b78def3f2ed78162f12d6
Comment 1•13 years ago
|
||
I can reproduce the high CPU usage with FF14 but not with Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Firefox/17.0 SeaMonkey/2.14a1 (animation: 4%CPU, scrolling:12% on my system)
Component: Untriaged → Layout
Product: Firefox → Core
Reporter | ||
Comment 2•13 years ago
|
||
Since waterffox has changed its site, here is a new site with the same issue :
http://grssam.com/
Try scrolling on this site. The CPU usage is almost 100%.
Reporter | ||
Updated•13 years ago
|
Summary: High CPU use on http://waterfoxproject.org/ → High CPU use on http://grssam.com/
Reporter | ||
Comment 3•12 years ago
|
||
This is no longer an issue. The CPU usage on the animation has reduced to almost nil now.
Please close this bug.
Reporter | ||
Updated•12 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•