All Sessions Lost! Tried IndexDB fix to no avail. TSM no longer autosaving.

[Alexander-jb]

Yesterday, while running a session that had been open for several days, I went to save it using TSM and discovered that all of my (many) sessions were gone. I saw no error messages, and I could/can manually save a session. It appears, however, that all auto-save function is not working---both saving every __ minutes, and saving session when closing browser. Both of those options are checked in settings. I am hoping this might be a key to what error is occurring.

Looking through these posts, I have followed the steps listed in the IndexDB error post (https://github.com/sienori/Tab-Session-Manager/wiki/IndexedDB-Error), as this seemed most promising and had helped many people with a similar issue. Unfortunately, when reopening FF and looking at TSM, sessions are still not showing up. Oddly enough, since doing this I have gotten the IndexDB error a number of times (currently not getting this error).

Unlike some others, my 1782160246ssensosi.files folder has a decent number of files in it, and my 1782160246ssensosi.sqlite file is 2.2MB. Not sure if it is all of the saved sessions or not, and if this even matters, but the dates on these files do seem to match up with the main period that I was utilizing TSM.

I am hoping that since these files seem to be here that there is some way to recover them, even though the replacement in storage/default method has not worked.

As many others with this issue have mentioned---this bug is core to the basic functionality and premises of anyone using TSM. This is information we need saved for a reason. For me personally, I was using TSM to clear-out and organize online research information from a number of devices. The volume of information I was working with was accumulated over years, and took a massive number of hours to transfer into TSM over many months. Now this is all lost. I understand that a backup function has been added, but it should be utilized in the default functioning of the add-on until this bug is totally resolved. Alternatively you should have a major warning in the description of the add-on that this bug exists and to not use TSM for long-term/important organization/storage--but again, why use it at all then?

Thanks for any help.

some background--
As mentioned above, I had a currently running session from which I had opened TSM previously with no issue. No updates to my computer, browser, or to TSM. Nothing had been restarted, etc.

• Platform (OS): MacOS High Sierra 10.13.6
• Version of browser: FF 68.0
• Version of Tab Session Manager: TSM 6.3.0

[Alexander-jb]

I have repeated the steps from the IndexDB troubleshoot page a few more times with no effect. Now that I have the copy of the storage folder with the matching TSM Internal UUID, is there any risk in deleting and reinstalling TSM? is there any possiblity of any session info being stored anywhere other than in that folder in the storage folder of my FF profile/root directory? I don't want to risk losing anything that might be recoverable by doing this.

Since TSM is allowing me to save sessions, but the autosave functions are not working at all, I am starting to wonder if uninstalling might help deal with whatever error is going on. I can then retry the steps of copying the old sessions back into the storage/default folder.

Thanks

[sienori]

I commneted: #677 (comment)