search

Chrisi75 / tabgroupsmanager

Automatically exported from code.google.com/p/tabgroupsmanager
1 stars 0 forks source link

Please recommend alternative of TGM - I CAN'T LIVE WITHOUT IT! #44

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Recently TGM appeared to have STACK related problem......Memory usage totally 
fucked up!

It will fail to save session/ run during normal use.
Also it will lost all of its session data even after firefox closed.
The only solution is to restore a former backup...

Please, I know rewrite this addon is a HUGE workload, and I won't request that. 
I know you guys are doing volunteering job...

All I want is an alternative addon of firefox/chrome

Please, if you know any(it has to be at least as good as TGM), please let us 
know!

I have more that 1000+ tabs and groups....

Original issue reported on code.google.com by a29988...@gmail.com on 16 Apr 2014 at 8:02

GoogleCodeExporter commented 9 years ago 
As far as I can see, you did not state the version of Tabgroupsmanager that you 
are using. Which one do you refer to?

If you are using a version below 2013-07-07-002, then you can try that version. 
It worked for me with Firefox 26 (not with 29 though)

Original comment by klausth...@googlemail.com on 5 Jun 2014 at 7:58

GoogleCodeExporter commented 9 years ago 
Version 29 has changed many things in UI and some fixes are needed in order to 
work with TGM. 
I can reproduce some of the lastest issues in my linux box so I hope to have a 
working fix in two/three weeks (sorry insanely busy with work and wont be able 
to do it before :(  ).

We need to talk also to make alot of changes and improvements in our release 
line (which is zero since these are difficult times). One of my thoughts is to 
change the current repository from subversion to git. I think it will be better 
in order to share new tgm versions and enable people to fix or fork it a lot 
easier than using svn.

Original comment by blacksha...@gmail.com on 5 Jun 2014 at 8:10

GoogleCodeExporter commented 9 years ago 
Do we have a release line?

There was no big changes with Fx29 in relation to TGM code. I have my own 
version and it was not necessary to modify them for the new Australis design. I 
only installed the addon classic theme restorer to get the old design back.

The memory problem is a Fx problem in session store processing. Sadly we have 
no regression range since when the memory problem was started and no 100% way 
to reproduce this failure. In fact to solve this, we need a way to reproduce 
this failure.

https://bugzilla.mozilla.org/show_bug.cgi?id=581510

Original comment by micha.go...@arcor.de on 5 Jun 2014 at 3:56

GoogleCodeExporter commented 9 years ago 
Main problem is FF is saving a lot of garbage in json format in the session 
file, filling it with a lot of mb. Sometimes the session could be corrupted 
because of bad json handling or leaks in the code. 

In the past tgm john and me talk about possible solutions but there arent easy 
ones.

One of the best ways would be to make our own session management using one of 
the best databases like Redis, MongoDB or MySQL, instead of the default sqlite 
engine and json parsing.

Original comment by blacksha...@gmail.com on 5 Jun 2014 at 4:03

GoogleCodeExporter commented 9 years ago 
Yes i have measured a tab on a google page and added only a word to the search 
terms. Got 70KB new data. They stored a lot of DOM data, likely also on other 
pages due history their reasons. Also a firefox related problem.

Found a tab here which was not updateable with latest history changes. At next 
fx start, there was always the page available before my change.

Isolated the tab by closing all other groups/tabs and got reduced 
sessionstore.js from 7MB to 590KB. This means from 160 Tabs & 7MB was 590KB 
related to this tab.

But this was still to big for one tab...investigated the file and found a lot 
of pages there which was not displayed in the TAB history and sure not opened 
in this tab. But only one tab was visible in Fx. It seems that there was a lot 
of old stuff in the sessionstore.js. Something is going wrong here.

Maybe this was caused by code changes in the past at mozillas side. Decide, it 
is time to cleanup.

Saved all groups & hibernated groups to bookmarks (and closed/deleted them) and 
deleted sessionstore.js. Reopened my bookmarks in new groups and will observe 
what happens with the memory failure now.

My personal opionion is, TGM should not write to FX sessionstore and only write 
to his own files. And we need also no session data in TGM related files for 
open tabs  because we have the FX sessionstore file. For open tabs it would be 
sufficient to save the TabID and group assignment. Maybe for hibernated tabs we 
should save history.

Original comment by micha.go...@arcor.de on 6 Jun 2014 at 1:33

GoogleCodeExporter commented 9 years ago 
Yes micha, TGM is making an horrible work when its saving the session. Its 
saving all the tab information that firefox creates, like all its cache and 
settings. The improvement we discussed a lot of time ago was the same you have 
seen, just saving the id and group, however it will require a deep look into 
the code and changing the way TGM handles it.

Original comment by tabgroup...@gmail.com on 20 Aug 2014 at 10:54