With latest Chrome update start to see this problem myself, seems that this is something new that was introduced with Chrome v26, yet cannot understand meantime how to reproduce this bug surely.

Any ideas how to reproduce this bug appreciated. Yet i will catch it in the end anyway : )

> I see a lot of errors in the console for the background page for the extension 

Ignore them please, most of them is not real errors

Must be fixed of course to not produce the junk in the console, this is already done in next major release, which is not released meantime.

As for tabs that stuck - that's really interesting, never saw such behavior on my pc, and it was never reported before. if you find a way to surely reproduce this please let me know.

Also thanks for this follow up, i was not known that it is not working if "Save HTML only" is used to save the  tree. Will be know now what to answer on similar requests.

Thanks : )

Best regards

PS Hope you don't forget to click 5 stars in reviews section ; )

Its look like you are not save the tree by Ctrl-S but use some other method, that only take the source. Not the generated by script content.

What version of Chrome do you use?

If you have a system drive backup you most likely already performing the backup of the Chrome profile.

Really strange, just tried - saved perfectly ok for me. It is actualy not the TO save the file but Chrome. So i cannot understand how it is possible that if tree is present in the window it was not saved in file.

Do you save it by Ctrl-S ?

As for internal data backup, consult this:

https://groups.google.com/d/msg/tabs-outliner-support-group/eKubL9Iw230/wQXOP1m90NoJ

soon there will be also an a Cloud backup 

meantime i just recommend to backup the full Chrome profile everyday.

Browser crash for me every week or something like this, i have tons of open windows always, yet i never seen that TabsOutliner lost any crashed window content. The empty windows artifacts i was saw several times and check this situation - they are not represent real crashed windows. 

The green one is the windows that was crashed or closed (through close all windows button) last time the TabsOutliner was open.

So if you have several crashes in one day, or just close the browser completely in that day several times (the TO has the problem that it's treat last visible windows on Chrome close as crashed, they not really crashed, just incorrectly detected as such) then it was show in green only the windows which was crashed/closed last time.

The empty windows is very unlikely was contained any crashed tabs. That is also an artifacts which appear sometimes on complete Chrome close.