Page MenuHomePhabricator

Recovery of edits after a crash not working in some cases
Closed, DeclinedPublic

Description

I've been having system problems lately, and crashing a lot. Before using VisualEditor, Chromium and Firefox saved my edits when restoring sessions, as long as I am using a persistent login. When using VisualEditor, they are unable to do this. Some type of recovery of in-process edits would be a really nice feature. I think at least for the time being, the lack of this feature is going to prevent me from using it anymore, maybe forever.

Event Timeline

Esanders changed the task status from Open to Stalled.Mar 12 2019, 4:04 PM
Esanders added a subscriber: Esanders.

VE has an autosave feature that keeps all your changes stored in sessionStorage. If your browser crashes and you recover the same tabs it should restore your edits. You should be able to simulate a browser crash from your OS's task manager, or by going to chrome://crash.

If you can reproduce making edits -> crashing the browser -> not having those edits recovered on reloading the same tabs, then please update with more instructions.

To clarify, is this about browser (or browser tab) crashing, or about your whole computer crashing (bluescreen, power loss)? I think in the second case we'll fail to recover the edits currently.

I think in the second case we'll fail to recover the edits currently.

Probably not if you have your browser set to restore your tabs.

Losing in-process edits (or any kind of work for that matter!) is frustrating and something we're actively thinking about [1] – thank you for raising this, @jamespharvey20.

As to the particular issue this task is responding to, like @Esanders mentioned:

If you can reproduce making edits -> crashing the browser -> not having those edits recovered on reloading the same tabs, then please update with more instructions.

...and @matmarex mentioned:

To clarify, is this about browser (or browser tab) crashing, or about your whole computer crashing (bluescreen, power loss)? I think in the second case we'll fail to recover the edits currently.

...sharing the steps that produced this issue would go a long way in helping us reproduce the issue you're experiencing en route to a potential solve.


  1. Exploring autoSave: We are exploring autoSave, and more specifically, our current implementation of it here (in case you'd like to follow the conversation in real-time): T218663: Consider switching from sessionStorage to localStorage for autosave
matmarex renamed this task from Feature: Recovery of edits after a crash to Recovery of edits after a crash not working in some cases.Apr 9 2019, 5:43 PM

To clarify, is this about browser (or browser tab) crashing, or about your whole computer crashing (bluescreen, power loss)?

Unfortunately closing this Phabricator task as no further information has been provided.

@jamespharvey20: After you have provided the information asked for and if this still happens, please set the status of this task back to "Open" via the Add Action...Change Status dropdown. Thanks!