Closed Bug 310916 Opened 19 years ago Closed 18 years ago

high CPU usage for directional scrolling

Categories

(SeaMonkey :: General, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 310912

People

(Reporter: user_2_2_2, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050702
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050702

when you scroll with directional keys in the about the "about:config" window
(and now this happens in "Bookmarks" sidebar as well), the CPU usage goes to 100%
(my computer is a 2.0GHz Pentium 4, downclocked to 1.2GHz)

Reproducible: Always

Steps to Reproduce:
1. open a new window or tab
2. type "about:config" in the address bar
3. click on a preference in the "about:config" window
4. scroll with the directional keys
Actual Results:  
CPU usage goes to 100 or almost 100%

Expected Results:  
CPU usage should be less than 40%
One bug should suffice.

*** This bug has been marked as a duplicate of 310912 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Bug 310912 is Firefox specific.  To dupe to it, it would need to be reassigned
to core.  However, a dependency is appropriate.
Status: RESOLVED → UNCONFIRMED
Depends on: 310912
Resolution: DUPLICATE → ---
Status: UNCONFIRMED → NEW
Ever confirmed: true
CPU jumps from 2% to about 30% for me.  Reports on Mozillazine indicate and
increase up to 40% for another person.  Mozilla 1.7.8 doesn't do this.
I duped this to the Firefox bug because the issue here is probably with XUL
trees. FWIW, I see the same CPU usage when doing this in 1.0 as I do in 1.5, in
Firefox at least.
(In reply to comment #2)
> Bug 310912 is Firefox specific.  To dupe to it, it would need to be reassigned
> to core.  

it has been moved to core

*** This bug has been marked as a duplicate of 310912 ***
Status: NEW → RESOLVED
Closed: 19 years ago18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.