> Or right-click a tab in that crashed window to reload it. 

And this i cannot understand at all.
Right click to reload the tab? Tabs are activated by dbl-click. If you need reload some already loaded tabs just save-close them (or their window) and then immedeately activate again.

Context menu with tons of features - planed.

But why you cannot reload all the tabs in the crashed window just by dbl-clicking on a window title?

I think this is also will solve finally frustrated problem with crashed windows on close. I am not solving it because actually many depend on this feature, especially novice users expect own windows to be saved on complete Chrome close. So this bug was worked as some sort of save.

The interesting question - is it worth to always save the closing window. Or only if they have any marks inside some tab (or changed title). I feel that only if they have some marks is the way to go....

Thanks again for a tip!

There is for example already exist undocumented Alt-DblClick for windows. It restore the window in a state it was saved - without the saved tabs which was saved in a moment of save. So will continue the Alternative tradition : ))

Or maybe Alt-Delete... this is more logical.

EXCELLENT!
Must admit i miss this information : )
I Just tried and seems it really works as expected.

Thanks for a tip - now i it really moves this feature to the top of my list for the next closest release.

Yet sometimes it really very useful to close the window but leave only marked items, so i will make this feature or optional, or Alt-CloseSave (in TO - green cross) will do it the old way.

Best regards!

Was thinking a little more about this and decide that maybe it is actually not a bad idea.

I think i will protect the windows from close (will convert to saved) if they placed anywhere in other nodes (not on a root level) or if they have any other node with some custom marks, or anything that is not a regular tab, or have a custom title.

The problem is that window close event come very after the all the tabs close events. So till complete close of all the tabs i will be unable to understaffed is this a window close or the sequential tabs close. Actually i will be unable to distinguish this cases at all, maybe only if i introduce some crazy logic which will measure speed of window close. But events from Chrome not always come immediately... And UI will also be unable to react on changes immediately.. but it is possible to counteract actually.. 

Worth to do this really. This will solve the biggest haters complain.

Anyway, If you will consider removing your 2 stars this will be very helpful and will motivate me to accomplish such changes sooner. Or at least in a better mood. Thanks.

> but programmers "like you" see enemies where you have friends.

Hay, man, maybe you will actually go and delete that your 2 stars? There is already enough people who leave 1 star really just of nothing... The rule to leave window as saved if it is in some group is just too complex to be practical. And there will be 10 times more users who will complain that it is ridiculous that they must protect windows by placing them in a group. Really. There better approaches. And they are in the work. 

We just waste there 2 hours out of nothing and even not revert the harm... that sad, please delete your review, it is mention the fact i write in bold letters in the first lines of the help, so really this will not very help some casual reviews reader. Even better - update it to 5 stars.

There is by the way no easy possibility in Chrome for extension to distinguish window close from the sequential manually close of its tabs. But this irrelevant actually. As leaving the window as saved after that is a bad idea.

The things you mention is well know. But the solution you propose was tried already and is very flawed, you just not see all of the consequences to have something always pined by default if it is placed in some group for example. Not to mention the learning curve for this behavior  Really don't want to waste my time on arguing, especially taking in account that much better solution is on the go and there many other more important problems now. 

If so happens that you can delete you rate, which drop the extension from the top rated, it will be cool. Do you spit on the people on a street which you don't like? No, you just move along. Give the rights to the users who like this approach to have own tool, and in a way as they like it. As you told - there tons of session managers already, nobody needs same tool for the tenth time. And find for yourself something else, if this is not what you want.

The extension does not do any harm, does not promise anything that they does not give. Yes, it's present new approaches, new way of dealing with some things, and it is in its core, its mission - it's handle the very important task, to lover the number of tabs for very specific users. You (and yes some others, you can find exactly same reviews with 1-2-3 stars easily), so happens to criticize the core principle. The behavior you mention is intentional and really very needed. The requirements to the user to form new behavior is also intentional. As they have real pain with the old and flawed one. Tons of users just say thank me because of this. Do your users write you emails on several pages with tons of thank you? And this is what important for me - it is solve the problem. Very painful problem.

And you principles about software design - good luck, go and design you software according to them. Wish you all the best with this. Just why need to harm the others, who you just don't understand, i don't know. You rate just make this thing impossible to find to several new people every day. Some of them desperately need this solution. This is just a regular organizer for you, but there others, for them It is a real lifesaver, exactly because of the principles you criticize. You just make impossible to meet some of them with this tool.

Yet of course all other users will be covered, just not today. But there will be as pin button, as many other ways to deal with this problem. At least i work on this.