Closed
Bug 550318
Opened 15 years ago
Closed 14 years ago
[Mac/Gecko/20100304 Minefield/3.7a3pre] Bad scrolling-performance and high CPU-usage in big/long menus of the Minefield-Preferences
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mehmetxsahin, Unassigned)
Details
(Whiteboard: [CLOSEME 2011-2-25])
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.3a3pre) Gecko/20100304 Minefield/3.7a3pre
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.3a3pre) Gecko/20100304 Minefield/3.7a3pre
Hello Firefox-Team,
in big/long menus of the Minefield-Preferences the scrolling-performance (two-finger-scrolling) is bad and has a higher CPU-usage compared Firefox 3.6.
Hardware: Macbook 3,1 / OS: 10.5.8
***SEE STEPS TO REPRODUCE***
Thanks and regards
Mehmet
Reproducible: Always
Steps to Reproduce:
1. open Minefield-Preferences
2. go to the tab "Content"
3. click on the select-field "Default font" so that the menu is to see
4. do "two-finger-scrolling" with the trackpad within the open menu
Actual Results:
Scrolling in this menu is jerky and not so smooth like in the official build of Firefox 3.6. Furthermor the CPU rises up to 50% (Minefield+WindowServer). Firefox 3.6 uses only 35% CPU (Firefox+WindowServer)
Expected Results:
A better smooth scrolling and not so high CPU-Usage !
Comment 1•14 years ago
|
||
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Also, ensure you update all your plugins (Flash, Reader, java, quicktime, etc) to the latest version available on the vendor's website.
Whiteboard: [CLOSEME 2011-2-25]
Fixed in Minefield. Please close this report !
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•14 years ago
|
Resolution: FIXED → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•