Great add-on - big trouble!

[GoogleCodeExporter]

Great add-on - big trouble!

So far Session Manager via TabGroupManager causes error messages as soon as the 
pre configured backup time period is due to be saved automatically. After the 
error message shows up, no further session backups are possible - neither 
automatically nor manually - until the browser process is terminated and 
relaunched.

I can't really recall when these errors occured for the first time or what may 
have caused them, but it seems to me that  Mozilla's browser updates are NOT 
taken into TGM's development process very well, if there is any at all recently.

1. I tried deleting and reinstalling Session Manager plus TGM on the the same 
FF Browser version: same errors!
2. I tried deleting and reinstalling both Session Manager and TGM to a new FF 
browser profile: same errors!
3. I tried by setting off all other addons one by one, to see if any of them 
may cause trouble as well or may serve as a trigger in conjunction: Flash 
proved to be a main cause for FF memory issues which in turn seem to trigger 
TGM / Session Manager Backup errors. 
4. I tried to avoid browser updates to prevent even further trouble, but the 
current TGM state is buggy as hell allready: same errors!

Error messages from today (collected within 20 minutes of session):

[quote]NS_ERROR_FAILURE
Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) 
[nsISessionStore.getBrowserState]

File: undefined
Line: 903
Stack:
TabGroupsManagerJsm.SaveData.prototype.saveFileFromTgmData@resource://tabgroupsm
anager/modules/TabGroupsManager.jsm:903:20
TabGroupsManagerJsm.SaveData.prototype.saveDataToFileInDataFolder@resource://tab
groupsmanager/modules/TabGroupsManager.jsm:658:9
TabGroupsManagerJsm.SaveData.prototype.backupByTimer@resource://tabgroupsmanager
/modules/TabGroupsManager.jsm:718:2
TabGroupsManagerJsm.SaveData.prototype.sessionBackupByTimerChange/event.notify@r
esource://tabgroupsmanager/modules/TabGroupsManager.jsm:731:38[/quote]

[quote]NS_ERROR_XPC_JS_THREW_STRING
out of memory'out of memory' when calling method: 
[nsISessionStore::getBrowserState]

File: undefined
Line: 903
Stack:
undefined[/quote]

[quote]Dieser Vorgang konnte auf Grund des folgenden Dateizugrifffehlers nicht 
ausgeführt werden:
undefined(undefined)

backup.session

undefined:undefined[/quote]

-----------------------------------------------------

Session Manager: 0.8.1.6
Installed TGM version:  2014.08.21.004
Tab Mix Plus: 0.4.1.5.2
FF: 35.0.1
MS Windows 7 Pro / SP1 (32 Bit)
Shockwave Flash: 17.0.0.188

Please fix!
Thanks!

Original issue reported on code.google.com by ulirey...@googlemail.com on 27 May 2015 at 4:32

[GoogleCodeExporter]

After updating TabGroupManager to version 2014.12.21.005 Beta I collect error 
messages like this now: 

Dieser Vorgang konnte auf Grund des folgenden Dateizugrifffehlers nicht 
ausgeführt werden:
Component returned failure code: 0x8007000e (NS_ERROR_OUT_OF_MEMORY) 
[nsIScriptableUnicodeConverter.convertToInputStream](NS_ERROR_OUT_OF_MEMORY)

backup.session

Private.writeFileNext@chrome://sessionmanager/content/modules/session_file_io.js
m:1796:14
Private.writeFile@chrome://sessionmanager/content/modules/session_file_io.jsm:17
70:2
Private.backupCurrentSession@chrome://sessionmanager/content/modules/session_fil
e_io.jsm:1335:0
this.SessionIo.backupCurrentSession@chrome://sessionmanager/content/modules/sess
ion_file_io.jsm:154:9
Private.observe@chrome://sessionmanager/content/modules/session_manager.jsm:372:
5

------------------------------------------------ 

Session Manager: 0.8.1.6
Installed TGM version:  2014.12.21.005 Beta
Tab Mix Plus: 0.4.1.5.2
FF: 35.0.1
MS Windows 7 Pro / SP1 (32 Bit)
Shockwave Flash: 17.0.0.188

Original comment by ulirey...@googlemail.com on 27 May 2015 at 5:48

[GoogleCodeExporter]

As so often mentioned here. This is no TGM bug. There is not enough memory in 
one block available for processing the json file. I have called the functions 
manually to reproduce it and if i close some other windows programs like 
Thunderbird, then it saves the Fx session. TGM holds many tabs and if you 
loading to much tabs with a lot of pictures or data you will run into this 
problem. Somewhere here i posted the bug number on bugzilla...

Original comment by micha.go...@arcor.de on 30 May 2015 at 12:23

[GoogleCodeExporter]

I have to correct, it is not a closed windows application which releases new 
memory, its a cleanup of the virtual address space which will be done from time 
to time automatically.

In fact as longer firefox runs and if more tabs we have open, the memory 
fragmentation is going ahead. If the smallest free block have only a 2MB size 
we get the out of memory error. Looks like there are situations where the 
cleanup will not be done fast enough as fx need a new big memory block. In the 
amount there is enough free memory but its fragmented.

In the attachment you can see some of the free blocks. Its going up and down 
with the biggest free block due the cleanup actions.

As you see its no part for addon developers to fix this.

Here you can read more:
bugslasher.net/2011/01/15/memory-exhaustion-even-if-a-large-enough-free-memory-s
egment-is-available/

Original comment by micha.go...@arcor.de on 7 Jun 2015 at 5:46

Attachments:

• fx.JPG

[GoogleCodeExporter]

I encountered these errors every couple of hours before I updated Greasemonkey 
to 3.3beta2. Greasemonkey caused memory leaks since 3.0 in newer firefox 
versions, thus this error of TabGroups Manager occurred much more often with 
it. After updating Greasemonkey I see this error much more seldom (though, of 
course it didn't disappear completely). 

Original comment by SergejBy...@gmail.com on 20 Jul 2015 at 2:32