Requesting crash recovery system

[GoogleCodeExporter]

Arora really needs a crash recovery system. Given how much I use open tabs
as TODO notes, I can't trust any tool without a way to save.

I suffer through Firefox's sluggishness and frequent crashing because
several crashes per day with reliable recovery is still better than one or
two crashes per week which are guaranteed to lose you tabs. (Yes, I leave
my desktop logged-in 24/7 and Arora running for a week or more in one run)

Aside from the tab corruption bug and the middle-click pasting bug I
reported, I think that's really the only major issue I have with Arora
0.9.0. (There are rendering issues, but those are QtWebKit's problem)

Original issue reported on code.google.com by stephan....@gmail.com on 17 Sep 2009 at 8:50

[GoogleCodeExporter]

Currently it has an autosave system so you shouldn't ever loose more then about 
three seconds of changes.  You 
can manually restore the last tabs from the history menu and in preferences you 
can have this be the default 
behavior on start.  It also detects recursive crashes so they don't cause you 
to never be able to start.  You can 
also manually save all tabs to a bookmark folder and open all bookmarks in a 
folder in tabs.  Anything else you 
think it should do?

Original comment by ice...@gmail.com on 17 Sep 2009 at 9:08

[GoogleCodeExporter]

Ahh. Probably best to make "Restore Last Session" more obvious and offer an 
"only
after unclean shutdown" mode to the automatic option.

As it is, the former got lost in the [non-]clutter (Yet more proof that 
selective
perception applies even to technically-skilled people actively searching for 
things)
and the latter got mistaken for "Restore my tabs if I cleanly exit the browser".

Original comment by stephan....@gmail.com on 18 Sep 2009 at 1:48

[GoogleCodeExporter]

Not to be insulting, but congrats on wasting my time and abusing my trust all 
in one
blow. 

I just discovered that I have to reassemble my entire set of tabs from history
because of an "ImageShack.us minus Javascript plus session restore equals crash 
on
startup" bug combined with "Even though you re-enabled JS, your saved session 
has
been sent to the shredder because it crashed your previous attempt at restoring"

Original comment by stephan....@gmail.com on 19 Sep 2009 at 12:50

[GoogleCodeExporter]

Having had time to cool down, I still feel that a crash recovery system which 
doesn't
fail safe is a fundamental violation of trust.

Original comment by stephan....@gmail.com on 19 Sep 2009 at 3:46

[GoogleCodeExporter]

Yes that should really be a question so you can bypass the check if you want 
to.  I have made that change.

http://github.com/Arora/arora/commit/63b4833b39a66a997be99369678a353a97c09d6e

Beyond that we could have a menu of the last five sessions or something, what 
do you think?

Original comment by ice...@gmail.com on 24 Sep 2009 at 3:51

[GoogleCodeExporter]

I'd suggest drawing inspiration from the Firefox Session Manager extension. 
When the
browser exits uncleanly and you restart it, you're given a dialog with the 
following
choices:

- Restore or not ("Cancel" and "Recover Session" buttons)
- Which crash to restore (Session Manager keeps a history)
- Which tabs to restore (Checkboxes. Lets you omit a window with a crashing 
plugin or
script)

Here's the official addons.mozilla.org screenshot of that particular dialog:
https://addons.mozilla.org/en-US/firefox/images/p/25573/1238531387

Original comment by stephan....@gmail.com on 24 Sep 2009 at 4:24