Mouse movement with javascript cause Minefield to use 100% of the CPU (or 1 core).

RESOLVED INACTIVE

Status

()

Core
Graphics
--
minor
RESOLVED INACTIVE
9 years ago
2 days ago

People

(Reporter: geeknik, Unassigned)

Tracking

({nightly-community, perf})

Trunk
All
Windows 7
nightly-community, perf
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4pre) Gecko/20090331 Shiretoko/3.5b4pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4pre) Gecko/20090331 Shiretoko/3.5b4pre

The javascript xeyes script @ http://www.javascriptkit.com/script/script2/xeye.shtml causes firefox 3.5b4pre to use 100% of the CPU while moving your mouse around the screen. Quit moving the mouse and CPU usage drops off to nothing.

Reproducible: Always

Steps to Reproduce:
1. Visit http://www.javascriptkit.com/script/script2/xeye.shtml
2. Move your mouse around the screen.
3. firefox.exe uses 100% of the CPU according to task manager.
Actual Results:  
firefox.exe uses 100% of the CPU

Expected Results:  
Firefox should not hog the CPU while executing this script.
(Reporter)

Comment 1

9 years ago
Behavior still exists despite all of the recent TM landings on the Branch.  3.5b4pre Build 20090416044319 on XP SP3.
(Reporter)

Comment 2

8 years ago
Still present in build 20100126052630 of Firefox 3.7a1pre. Move your mouse around the screen while this script is active causes Minefield to use 100% of 1 CPU core. Quit moving the mouse and CPU usage drops to zero. Moving to a more appropriate component.
Status: UNCONFIRMED → NEW
Component: General → Graphics
Ever confirmed: true
OS: Windows Vista → Windows 7
Product: Firefox → Core
QA Contact: general → thebes
Hardware: x86 → All
Version: unspecified → Trunk
(Reporter)

Updated

8 years ago
Summary: Javascript Xeyes script causes Firefox 3.5b4pre to use 100% of the CPU. → Mouse movement at this URL cause Minefield to use 100% of the CPU (or 1 core).

Comment 3

8 years ago
I can't say I see a huge problem. I see high cpu only rarely and randomly, and it's very brief - about 1 sec. However, IE is 0% cpu

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a4pre) Gecko/20100406 Minefield/3.7a4pre
Severity: normal → minor
Keywords: perf
Summary: Mouse movement at this URL cause Minefield to use 100% of the CPU (or 1 core). → Mouse movement with javascript cause Minefield to use 100% of the CPU (or 1 core).
I can reproduce this behavior in 7.0, I'm not sure if this is a big bug, because it performs fine, but perhaps there's room for a reduction in CPU usage, I'm not sure this is spending time in graphics specifically though, it would need some profiling.
(Reporter)

Comment 5

6 years ago
This behavior is still present in Firefox 16.0a1, it maxes out 1 core on my i7-920 while moving the mouse around the page.
(Reporter)

Comment 7

5 years ago
Even now, Firefox 29.0a1 still sees an increase in CPU usage from less than 1% w/o mouse movement to about 10%. Less than what it was before, but I'll leave it up to Bas to decide whether there is anymore room for improvement or if we just close this and move on to something else. ;)

Updated

5 years ago
Flags: needinfo?(bas)
(In reply to Brian Carpenter [:geeknik] from comment #7)
> Even now, Firefox 29.0a1 still sees an increase in CPU usage from less than
> 1% w/o mouse movement to about 10%. Less than what it was before, but I'll
> leave it up to Bas to decide whether there is anymore room for improvement
> or if we just close this and move on to something else. ;)

I'd rather not close this just yet. I'd still like to understand it even though it's not a high priority.
Flags: needinfo?(bas)
(Reporter)

Comment 9

2 years ago
Still seeing ~10% CPU usage w/ 51.0a1 (2016-09-17) (64-bit) and e10s enabled.
(Reporter)

Updated

2 years ago
Keywords: nightly-community

Comment 10

2 days ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 2 days ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.