CPU overloaded with no tabs open
If I surf all day with the current version of TFF 17, the CPU becomes overwhelmed, and it does not return to normal when I close all of the tabs. I'm certainly thrilled to have it of course, but this is the one thing that most affects usability.
While developers will undoubtedly appreciate the play-by-play coding action described in the blog, the typical end user probably just wants to know if there is going to be any long term performance advantage in switching over to the unstable branch. In other words, the Javascript performance becomes insignificant if threads are getting stuck in an endless loop anyway.
I would welcome any comments on how you see this issue being addressed in the future, and would like to know if there is any kind of extension which provides a more detailed description of what is going on "under the hood".
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Cameron Kaiser on 05 Apr, 2013 02:59 PM
I can't replicate this, so I can't give you any suggestions. You might look at what add-ons you have installed as some of them may do background tasks. However, with all windows and tabs closed, I don't see anything like this on any of the test systems.
2 Posted by G4A on 08 Apr, 2013 02:08 PM
When performance started to lag again, I tried to quit TFF. Only at this point did an unresponsive script notice appear. But it just hung there and I had to kill the process. (And half of the tabs were lost when I tried to restore the last session.)
I made a snapshot of the script error message; attached. (It looks like jid0-rx4n0POMA8t2l0QhMgX6BhbF3go is the QuickTime enabler). I have a crash report too if you care for it. I wonder if Mozilla will ever make FF automatically identify a problem extension!
(incidentally, extensions.sqlite also contains the local path this was installed from, which cant be relied on as a permanent resource, so I dont know why it stores that)
With regard to ordinary browsing, I also wonder why we cannot make the default behavior to suspend script execution on all tabs except the one that currently has the focus, just to speed things up on slow machines.
Support Staff 3 Posted by Cameron Kaiser on 09 Apr, 2013 12:22 AM
Something else is going on (it's possible it happened to time out when that specific extension was being executed). You can go ahead and post the crash report if you like, but without specific steps to reproduce it, there isn't a whole lot I can do to act on it. Please also ensure that you have not used the unsupported method to reenable plugins, as this can be a separate source of crashes or browser instability.
You could also try 20 to see if the same problem occurs. If it does, my next suggestion would be a profile reset (see below "How to reset your profile").
In reference to your final question, Mozilla has this on their to-do list, but the potential pitfalls and the modifications required are currently too great for us to implement it unilaterally (not only would we be responsible for the bugs, but it would hurt the maintainability of the browser). There are some add-ons that address it, but they all have drawbacks. Probably the best supported is this one, but YMMV: https://addons.mozilla.org/en-US/firefox/addon/suspend-background-t...
4 Posted by Jerzy on 14 Apr, 2013 01:34 AM
You can go to about:memory to find out what eats you RAM and if you scroll down, there is a button Minimize memory usage, maybe pressing it will help.