5 ms·

I disagree. I've had so many issues with the Firefox Developer edition I stopped using it and have switched to Opera for my browsing needs. Way more reliable

I disagree. I've had so many issues with the Firefox Developer edition I stopped using it and have switched to Opera for my browsing needs. Way more reliable, doesn't constantly hang and time out, and isn't a total resource hog like Firefox has become.

capitainenemo 6y ago
Speaking from personal experience doing user support in firefox IRC channel on freenode and formerly moznet, the vast majority of "resource hog" complaints are due to the user running AdBlock with a million block rules (or some similar addon). Occasionally it is a particular long running website with JS memory leaks though. Like a gmail pinned tab. In terms of performance, until recently a common issue was lack of default graphics acceleration on linux, requiring manually enabling layers.acceleration.force-enabled
- hermanradtke 6y ago
  How can someone determine this? I wonder Firefox itself does not tell me the resource issues are due to an extension.
  - gravitas 6y ago
    Firefox has a suite of `about:` URLs[1], one of them is about:performance which will show you the Task Manager (their name) which has a sort of CPU and RAM column. It even shows you when it's javascript on a tab chewing up resources and not the extension. [1] https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/The_about_protocol https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/The...
    - dblohm7 6y ago
      about:about is the fastest way to look these up. :-)
    - capitainenemo 6y ago
      I don't know if the situation has improved, but at least in past it seems about:performance has a problem picking out problems created by an addon doing a ton of DOM manipulation that chews up resources in the tab. Bisecting addons or my preference, a clean profile or safe mode, was usually what I suggested, but YMMV.
- dleslie 6y ago
  Firefox ought to have native blocking with a fast rules processing engine.

capitainenemo 6y ago

Speaking from personal experience doing user support in firefox IRC channel on freenode and formerly moznet, the vast majority of "resource hog" complaints are due to the user running AdBlock with a million block rules (or some similar addon). Occasionally it is a particular long running website with JS memory leaks though. Like a gmail pinned tab. In terms of performance, until recently a common issue was lack of default graphics acceleration on linux, requiring manually enabling layers.acceleration.force-enabled

hermanradtke 6y ago
How can someone determine this? I wonder Firefox itself does not tell me the resource issues are due to an extension.
- gravitas 6y ago
  Firefox has a suite of `about:` URLs[1], one of them is about:performance which will show you the Task Manager (their name) which has a sort of CPU and RAM column. It even shows you when it's javascript on a tab chewing up resources and not the extension. [1] https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/The_about_protocol https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/The...
  - dblohm7 6y ago
    about:about is the fastest way to look these up. :-)
  - capitainenemo 6y ago
    I don't know if the situation has improved, but at least in past it seems about:performance has a problem picking out problems created by an addon doing a ton of DOM manipulation that chews up resources in the tab. Bisecting addons or my preference, a clean profile or safe mode, was usually what I suggested, but YMMV.
dleslie 6y ago
Firefox ought to have native blocking with a fast rules processing engine.