4 ms·

The issue with Firefox is that some times the whole browser is freezing. That's what keeps pushing me back to Chrome, not performance issues.

by zimbatm 13y ago

mcdoh 13y ago
Chrome freezing is why I'm considering switching back to Firefox.
- cmpxchg8 13y ago
  Chrome also phones home all the time, which is why I stopped using it. I don't notice much performance difference between Firefox and Chrome anyway, and always use Noscript, Adblock+ and Disconnect.
matthiasv 13y ago
That is your issue with Firefox or your setup. I never had this for at least one or two years now, even with misbehaving scripts.
- ksec 13y ago
  Nope, It is a common issues with Firefox although it has been greatly reduced in the last year or so. The project to fix all this is called e10s. Moving Content, and UI etc to seperate process as well as OMTx ( Off Main Thread Everything ) where Firefox Dev trys to do everything in async style and move them off Main Thread. Progress has been slow. But at least they are working on it
- driverdan 13y ago
  It's a core problem with FF. Everything runs under the same process so a single site with slow / frozen JS will affect the whole browser.
- thelukester 13y ago
  matthiasv, I don't know what your secret is, only 1 tab open in 1 window open at time, JS disabled, or what, but this is a very real issue. I have Firefox installed on all 4 of my machines, work desktop, home desktop, laptop, and a netbook. 2 of which are fresh installs. On all 4 when I visit multiple HTML5 heavy sites, FF's UI gets unresponsive. Chrome and newer versions of IE do not suffer from this, and I'm pretty sure it comes from FF running in a single process. Chrome and IE have their issues too, like thrashing memory a lot sooner than FF, which is why FF is still the default browser on my laptop and netbook despite its unresponsive UI under heavy load.
yuvadam 13y ago
Did you take the time to search through open tickets or create a new one so that Firefox could improve?
cpeterso 13y ago
Do you have any add-ons installed? I'm not shifting the blame from Mozilla to the add-on developer, but it might pinpoint the problem you found. If add-ons are using slow APIs, then Mozilla can do something about it. For example, some synchronous add-on APIs have been replaced with async versions.
kevingadd 13y ago
Are you visiting websites containing the Flash Player plugin? If so, try killing the plugin-container process. Flash continually gets less stable and Firefox can only do so much to compensate when the plugin hangs (plugins are intentionally allowed to insert themselves into the message loop, which makes it possible for them to hang a browser)

The issue with Firefox is that some times the whole browser is freezing. That's what keeps pushing me back to Chrome, not performance issues.

by zimbatm 13y ago

The issue with Firefox is that some times the whole browser is freezing. That's what keeps pushing me back to Chrome, not performance issues.

mcdoh 13y ago

Chrome freezing is why I'm considering switching back to Firefox.

cmpxchg8 13y ago
Chrome also phones home all the time, which is why I stopped using it. I don't notice much performance difference between Firefox and Chrome anyway, and always use Noscript, Adblock+ and Disconnect.

matthiasv 13y ago

That is your issue with Firefox or your setup. I never had this for at least one or two years now, even with misbehaving scripts.

ksec 13y ago
Nope, It is a common issues with Firefox although it has been greatly reduced in the last year or so. The project to fix all this is called e10s. Moving Content, and UI etc to seperate process as well as OMTx ( Off Main Thread Everything ) where Firefox Dev trys to do everything in async style and move them off Main Thread. Progress has been slow. But at least they are working on it
driverdan 13y ago
It's a core problem with FF. Everything runs under the same process so a single site with slow / frozen JS will affect the whole browser.
thelukester 13y ago
matthiasv, I don't know what your secret is, only 1 tab open in 1 window open at time, JS disabled, or what, but this is a very real issue. I have Firefox installed on all 4 of my machines, work desktop, home desktop, laptop, and a netbook. 2 of which are fresh installs. On all 4 when I visit multiple HTML5 heavy sites, FF's UI gets unresponsive. Chrome and newer versions of IE do not suffer from this, and I'm pretty sure it comes from FF running in a single process. Chrome and IE have their issues too, like thrashing memory a lot sooner than FF, which is why FF is still the default browser on my laptop and netbook despite its unresponsive UI under heavy load.

yuvadam 13y ago

Did you take the time to search through open tickets or create a new one so that Firefox could improve?

cpeterso 13y ago

Do you have any add-ons installed? I'm not shifting the blame from Mozilla to the add-on developer, but it might pinpoint the problem you found. If add-ons are using slow APIs, then Mozilla can do something about it. For example, some synchronous add-on APIs have been replaced with async versions.

kevingadd 13y ago

Are you visiting websites containing the Flash Player plugin? If so, try killing the plugin-container process. Flash continually gets less stable and Firefox can only do so much to compensate when the plugin hangs (plugins are intentionally allowed to insert themselves into the message loop, which makes it possible for them to hang a browser)