Re:Firefox’s speed with large numbers of tabs leaves Chrome ...
by jmontano on Tuesday July 25, 2017 @06:16PM
(#14852358)
> It would be really nice if browsers kept a history of your last N window + tab sets and allowed you to restore them whenever you wanted, rather than only the last one, and only after it thinks it crashed. Because when it gets this wrong, you usually have no recourse.
This is possible using Tab Mixer Plus extension for Firefox
Re:Firefox’s speed with large numbers of tabs leaves Chrome ...
by y4mi on Tuesday July 25, 2017 @03:39PM
(#14851189)
urm, chrome does exactly that?
its almost 10 windows i think. closing a window with 10 tabs still counts as a single entry.
The menu is nested into history and works on successive crashes.
Re:Firefox’s speed with large numbers of tabs leaves Chrome ...
by ohazi on Tuesday July 25, 2017 @03:47PM
(#14851253)
This still doesn't do what I want. If I have 5 windows open with 5-20 tabs each, and force a crash, I can recover them via this menu. It's tedious because I have to do them one by one, but it works.
But if I crash chrome, relaunch, don't recover or open a different set of tabs before recovering, then force a crash again, the menu is blank.
I'm not going to rely on something this finicky. Compare this to history -- it's there, in chronological order, until you clear it. That's how this should work.
Sometimes it fails, or Chrome crashes a second time after relaunching, but before you were able to restore the tabs, causing the next restore to open a blank window instead of your tabs from two crashes ago. This happens more often than I'm comfortable with.
It would be really nice if browsers kept a history of your last N window + tab sets and allowed you to restore them whenever you wanted, rather than only the last one, and only after it thinks it crashed. Because when it gets this wrong, you usually have no recourse.