All you mention is valid concerns.

To solve them need implement reassociation. Yet this issue have a lot of corner cases to do it correctly, and it might bring a lot of support hasle. So i am waiting for this Chrome feature to be done:

https://code.google.com/p/chromium/issues/detail?id=176030&can=5&colspec=ID%20Pri%20M%20Iteration%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified

(please stare it by the way)

It is exactly about this cases you mention and it must make this reassociation after shut down/restart/crash a one hour toy task for me.

It was promised that the work is going on, yet seems it is stuck. So maybe need to stop wait and to implement ugly workaround in TO. ( Yet it will be cool if actually somebody just do it in Chrome sources. The other people who comment on there chromium issue thread is authors of other well know session managers - so this will be very beneficially for many extensions.)

And, just a quick note about this your paragraph:

>>

but when i do so (by double-clicking on the old window-session), not only the active, but also the suspended tabs are re-opened...or am i missing some knowledge here?

>>
There exist alternative restore. Double-click with ALT pressed - it will restore only the tabs that were open at a moment of save/crash.

Best.

First of all. You most likely talk not about this bug but about something else. If you have some suspended windows on restart, without crashed labels, that because they are normally saved on exit. This happens automatically in many cases - for example if window have custom label, or note inside, or is placed in some other node. This is expected behavior.

As for for windows that labeled crashed on close - the unfortunate truth is that this feature is just impossible to fix completely without changes in Chrome itself.

When Chrome Closing it abruptly shut down all extensions without giving them chances to save any data to disk or in other storage.

So on restart extension cannot determine are windows were crashed or closed normally. From extension perspective they all looks like suddenly disappeared.

Some workarounds were done that help with that but they all have limits.

The other story is that maybe on restart need reassociate such crashed or normally suspended windows with reopened by Chrome copies. This is possible of course... 

Also there is also some workaround. 

by making Chrome continue to run in background

the crashed windows must never occur at all

http://pctonic.net/improve-chromes-startup-time-by-installing-a-background-app

the problem why they reported as crashed is because on Chrome exit extension is not be able to write anything to disk. To flag the windows as normally closed. There is actually some workarounds for this was implemented recently. But sometimes even them seems fail.

Yet not sure we a talking about same.

Can you mention the version of you TO extension and the version of Chrome. The crashed windows on close must not occur anymore

sorry, that is actually possible to fix, and even planed, but....

there is more important task meantime to finish and release very asked synchronize capabilities.

Yet i hope in a month i will come to this problem.

kickstarter is a good idea, i am actually planing it, but for a more rich offline features, if the synchronize will not give any serious funds to enable me make this a full time job.

By the way, what monthly fee will be too big for you for this, 

and also what you will consider a bargain price?

At least somebody still wait : ))

Hard working on this. 

Yet first version of this feature maybe will not be so rich as you describe.

Do you really need to have all devices in one outline?
I plan this meantime as separate, yet accessible from the web, trees, one tree per device, updated in real time. Almost ready.

And as for mobile - as i know the Chrome for mobile does not allow extensions. So not sure how it will be possible to make mobile tabs online.

The Phantom Tabs Bug must be fixed for now in v0.4.72 

> Can you post here when you post the update with the fix? 

Sure, i will set fixed state for the bug. this must lead to notification for all the participants.