several windows users in the support forums have reported that firefox is becoming slow, using high cpu ressources & mouse movements are generally laggy when the firefox window is running on an external dvi/hdmi-connected monitor in a dual-screen setup.
this seems to have started with the firefox 18 release & apparently isn't related to hardware acceleration, since it's also happening in safemode/with HWA disabled and reportedly with gpus from different vendors.
I'm one of those several users. For me, safemode DOES prevent the problem. However, manually disabling all addins or turning off HWA in firefox or even disabling all accelerations in the display driver DOES NOT prevent the problem. Idle CPU utilization for firefox on my machine usually sits at about 2.5-3.5% (according to ProcessExplorer); I find that I can drive it up to 20-25% by moving the mouse pointer quickly across links or menu items that need to change appearance upon mouseover--but only if the window is open on the second monitor (which I believe is VGA connected). In safemode, by way of contrast, CPU utilization is a fairly constant 8-9%. The net effect is that for me, firefox is unusable on the second monitor.
aebirner, could you use the tool mozregression (see http://harthur.github.com/mozregression/ to use it) to find a possible regression range since FF17 or FF18?
(ex: mozregression --good=2012-08-01)
It would be useful to find a regression.
Hmmm. All of the nightly builds worked just fine. I had trouble getting CPU utilization above 5%. What should I try next? Disabling all extensions and plugins one by one?
You can start by testing with a fresh profile with FF18 (see https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles)
Using a fresh profile doesn't fix the problem for me.
I tried mozregression and I get the same problem with nightly builds at least as old as 2010-01-01. :(
dragonq0105, did you test with HWA disabled?
The nightly build from 2010-01-01 doesn't have hardware acceleration as far as I can tell.
Something very interesting: if I have Chrome open at the same time as having Firefox open, the Firefox mouse slowness completely disappears (in both 2010-01-01 and 18.0.2)!
From the "I hate when that happens" dept: No longer able to reproduce, as of FF19 release.
That said, scrolling is still noticeably slower/jerkier on the second (VGA-attached) monitor than on the built-in LCD panel. The mouse stickiness is gone, though. I'm back to using Firefox on my big monitor, again.
aebirner, do you know if previous versions (FF15-16-17 or lower) got this issue about scrolling jerky on the 2nd monitor?
If it was fine in the past, can you file a new bug report and use mozregression tool (see http://harthur.github.com/mozregression/) to find a regression range, please.
Firefox 19 doesn't fix the issue for me. I still need Chrome open (even minimised) to eliminate the jerky mouse movement.
Be sure your drivers are up-to-date.
I can't think of any other drivers to check. Chipset, mouse and graphics drivers are all the latest available.
(In reply to Loic from comment #11)
> aebirner, do you know if previous versions (FF15-16-17 or lower) got this
> issue about scrolling jerky on the 2nd monitor?
> If it was fine in the past, can you file a new bug report and use
> mozregression tool (see http://harthur.github.com/mozregression/) to find a
> regression range, please.
No previous versions of FF had this problem. Both issues (mouse stickiness, slow scrolling) first appeared in FF 18; the mouse stickiness disappeared for the most part in FF 19, but the scrolling issue remains. There now seems to be a general slowness to the initial rendering of a page on the second monitor; scrolling and mouse movements are noticeably jerky while the page is rendering, but much less so after the page is initially displayed. I will file a new bug report for these latter issues.
I'm also having this issue, and it's happening on a desktop. I think I might have an idea as to the cause.
First of all however: I'm running in safe mode with HWA off with the latest nightly (22.0a1 (2013-03-14)), and the problem still occurs.
I've got two graphics cards: an i7 2600k's built-in intel HD3000, and an nvidia 7600GT.
The problem only occurs on the two monitors attached to the second GFX adadapter (nvidia 7600gt).
Could it be that the people with laptops that are seeing this have one of those dual-mode GFX laptop setups with both an onbord and add-on GFX card? Those aren't uncommon for power saving / performance tradeoff reasons.
Nice idea but my laptop, which still suffers from this issue, doesn't have a second GPU. It only has the IGP on the i5-430m, with the external monitor connected via HDMI.
I can confirm this issue in the latest Firefox 21 beta. I'm running on Windows 8 64-bit with two video cards (Intel graphics and Geforce 8400GS). When Firefox is running on the monitor powered by Intel graphics, everything is perfectly smooth. If Firefox moves to one of the monitors on the Geforce 8400GS, the mouse movement is very jerky.
Let me know if there's any additional information I can provide.
This is still a problem for me with FF 21 on WinXP SP3. I first uninstalled FF, removed the various installation and profile directories, and deleted all the registry keys that I could find; then I reinstalled from a fresh download. Still the same effect on my dual-monitor setup: Performance is great when the browser window is on the laptop LCD, but is slow as molasses in January when the window is open on the VGA-attached second monitor. Disabling hardware acceleration has no effect.
My computer is a Lenovo T420s. The device manager says the display is an "Intel(R) HD Graphics Family". The driver is version 18.104.22.16861, dated 5/2/2011. Monitor 1 is the laptop LCD, which is set to 1600x900 pixels w/ 32-bit color (and on which I see no performance problems). Monitor 2 is an external VGA-connected LCD, set to 1680x1050 at 60 Hz, also w/ 32-bit color. I have also duplicated the problem when using a Samsung T240HD at 1920x1200 as Monitor 2.
Almost 3 years later, do you still see this problem?
The machine with the iGFX and discrete GFX card that used to exhibit this problem for me has been retired, so I can't tell whether this problem still exists.
I haven't seen this bug in a long time, nor do I have the original computer I reported the issue on.
Closing this bug based on the above two comments. If anyone can reproduce this in a current Firefox version, please reopen and update the information in this bug report. Thanks.