You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before submitting the issue, please check that your version of TabGroups
Manager is the lastest stable one. (Check it in Firefox Extensions).
What steps will reproduce the problem?
1. Open the performance tab in task manager (Windows) or other system
monitoring tool
2.Start a Firefox session with a very large number of tabs in suspended groups
(or maybe just with a very large number of tabs)
3.Observe that the RAM usage climbs to a very high peak while the tabs are
loading, then suddenly drops to a more reasonable level.
What is the expected output? What do you see instead?
The problem is that if you do not have the necessary amount of available RAM,
the system starts using the page file instead, which causes the whole system to
slow down to a grinding halt. Firefox can take 5 minutes or more to open if
this occurs. Once Firefox is running the RAM usage is at a much more reasonable
level.
I had to put extra RAM in my machine solely because of this issue. And I always
start Firefox as the first application so I have the necessary RAM buffer.
System Info:
What version of TabGroups Manager are you using? Beta 005
What Operative System are you using? 32 or 64 bits? Win 8 x64
What version of Firefox are you using? 34.0.5
Are you using any other tab extension like Colorfull tabs, Multiple Tab
Handler, TabMix Plus..? No
Please provide any additional information below and screens capture if
possible.
Original issue reported on code.google.com by [email protected] on 7 Mar 2015 at 12:42
It just occurred to me that this might be a Firefox issue rather than a TGM
issue - I really do not know. I have never tried running Firefox with a huge
number of tabs without also having TGM installed.
Original issue reported on code.google.com by
[email protected]
on 7 Mar 2015 at 12:42Attachments:
The text was updated successfully, but these errors were encountered: