TG is broke again, like after FF 34? update

[GoogleCodeExporter]

Before submitting the issue, please check that your version of TabGroups
Manager is the lastest stable one. (Check it in Firefox Extensions).  Yes

What steps will reproduce the problem?
1. Tabgroups is now doing the same as it was when FF 34 came along.  The recent 
update to 37 has now made all tabs appear in all groups.
2. I appear to have the latest version of TG installed. (Dec 2014.12.21.005
3. On one of my machines, have been getting memory handler issues from TG the 
last few days - perhaps another symptom.
4. I hope that someone is able to fix this - it is a tremendous product!



System Info:
What version of TabGroups Manager are you using? 2014.12.21.005
What Operative System are you using? 32 or 64 bits?  64
What version of Firefox are you using? 37.0.1
Are you using any other tab extension like Colorfull tabs, Multiple Tab
Handler, TabMix Plus..?  TabMix Plus


Please provide any additional information below and screens capture if
possible.

Original issue reported on code.google.com by [email protected] on 15 Apr 2015 at 6:10

[GoogleCodeExporter]

With fx37 and beta 105 looks all ok here. 

All tabs in all groups would indicate that there is something destroyed with 
tab hide. If this is the case, on group switching you should have error message 
in console output. What is if you disable all other addons?

Original comment by [email protected] on 15 Apr 2015 at 8:53

[GoogleCodeExporter]

Hi bradleymc734, Im currently using Firefox 37.0.1 and everything seems to work 
right. I have about 300 tabs in different groups. I usually see memory problems 
after more than +200 tabs, and of course, always using firebug.

Original comment by [email protected] on 15 Apr 2015 at 10:31

[GoogleCodeExporter]

I can try disabling addons, but like my lastpass & tabmix plus, etc.  Haven't 
added any new addons in probably six months.

To the other comment, the machine giving memory errors is not exhibiting the 
tabgroup issue (all tabs in all groups), just memory.  I'll try and capture 
that screen next time it happens and share it.

The machine with the groups issue is not giving memory errors (in fact has many 
fewer tabs open).  Both have FF37.0.1

Thank you both for your ideas!

Original comment by [email protected] on 15 Apr 2015 at 11:49

[GoogleCodeExporter]

Well, a clue surfaced where one of the two windows I had opened was responding 
normally, while the other was behaving as explained previously.  By hibernating 
each tab group from the bad browser window (until all were closed and the 
window closed) I was able to reopen them in a new browser window, where they 
responded properly.  Note that I did not disable any addons or anything else.  
I suspect there must have been some corruption somewhere, and am not 
intelligent enough to know where.  But if anyone else experiences this, it may 
be worth trying what I did; everything now appears to be working correctly.

Thanks to those that attempted to help - much appreciated!

Original comment by [email protected] on 18 Apr 2015 at 6:46

[GoogleCodeExporter]

That's an interesting approach Bradley.  This happens to me (especially after 
FF Update).  Will try to do this now as it seems to have happened with FF39 and 
b105 recently.  Also using tabmix, so will try disabling that as well.

Original comment by [email protected] on 8 Jul 2015 at 3:19