Autosave and Crash Recovery
The editor protects unsaved work in three ways:
- Autosave keeps a snapshot of every modified document, so that a crash, a power cut or a killed process does not lose more than the last few seconds of work.
- Recovery offers those snapshots, document by document, the next time you open the project.
- Restore Previous Version brings back the version a document's file had before its last save. See Saving documents.
Autosave never writes to your documents. Your files only change when you save.
How autosave works
When a document is modified and you have not edited it for 30 seconds, the editor writes a snapshot of it in the background. Each document has at most one snapshot, and every new snapshot replaces the previous one.
The snapshot is removed again when:
- you save the document,
- you undo back to the saved state, or
- you close the document. Closing a modified document without saving means you chose to drop the changes.
Snapshots, together with the files the editor uses to notice an unclean exit, live in the Autosave folder of the project. The editor writes a .gitignore and a .dvignore into that folder, so version control does not pick it up. The snapshots use their own .plAutosave extension, so the asset curator ignores them.
Autosave has no settings. It is active whenever a project is open for writing. An editor that has the project read-only does not autosave.
Recovering after a crash
If the editor did not close normally the last time the project was open, the Recover Unsaved Work dialog appears when you open the project again. It shows when there are snapshots to recover, when the editor crashed while opening a document, when it crashed several times in a row, or when there is a crash report you have not seen yet.

The dialog after a crash with no unsaved changes. When autosave snapshots exist, they are listed below the crash notice with their Recover and Discard actions.
The list on the left has one entry per document that had unsaved changes. A flag next to an entry tells you something about it:
| Flag | Meaning |
|---|---|
| Open at crash | The editor ended while this document was being opened or was the active document. |
| File missing | The document's file does not exist any more, so the snapshot can't be opened as the document. |
| Disk is newer | The file was saved after the snapshot was taken. Recovering would bring older work back, so the default is Discard. |
Select an entry to see the times of the snapshot (Autosaved) and of the file (File on disk saved), and the list of Changes since the file was saved. For each document choose an Action:
- Recover opens the snapshot as the document, marked as unsaved. The file on disk changes only when you save it.
- Discard deletes the snapshot. The file on disk stays as it is.
Then close the dialog with one of its buttons:
| Button | What it does |
|---|---|
| Recover | Applies the action chosen for each document. The label reads Discard when every document is set to Discard, and Continue when there is nothing to recover. |
| Discard All | Deletes every snapshot after asking you. The documents on disk stay as they are. |
| Decide Later | Keeps every snapshot and asks again at the next start. |
| Safe Mode | Only shown during a crash loop. See below. |
Below the list, Don't reopen last session's documents stops the editor from reopening the documents that were open in the last session. If the crash happened while a document was being opened, the dialog says so (The last session ended while ... was being opened) and this option is on by default, so the same document does not crash the editor again.
A recovered snapshot stays in the Autosave folder until you save or close the document, so it is not lost if opening it fails.
Getting out of a crash loop
If the editor ended unexpectedly two or more times in a row, the dialog shows a warning (The editor ended unexpectedly N times in a row) and offers Safe Mode. Safe Mode restarts the editor without reopening any documents. The snapshots stay, so you are asked about them again at the next start.
A session that runs for five minutes without crashing resets the count.
Crash reports
The editor installs a crash handler when it starts. What it does with a crash depends on how the editor was built:
- With a Sentry DSN (builds made with
PLASMA_SENTRY_DSNset), the crash is reported to the developers through Sentry. If you were offline, the report is sent at a later start. - Without a DSN, the editor writes a mini-dump to
%APPDATA%\plEngine Project\Editor\CrashDumpson this computer and sends nothing.
The next time a project opens, the recovery dialog shows an Editor crash card for the newest crash you have not been told about yet. It lists when the crash happened, the editor version and build, the project's packages, and the Crash dump file with Show in Folder and Copy Path buttons. A line on the card says what happened to the report:
- The crash reporter sent this crash to the Plasma developers.
- This build does not send crash reports: the dump stays on this computer. Please attach it when you report the problem.
- It is not known whether this crash was reported. The dump is on this computer.
The card also reminds you that the crash itself was not recovered: the dump is for finding out what went wrong, and unsaved work only comes back from the autosave snapshots. Decide Later keeps the crash report, so it is shown again at the next start.
If you report a crash, attach the dump file and the editor log.
Troubleshooting
| Symptom | Cause |
|---|---|
| A document is not in the recovery list | It was saved, closed, or back at its saved state when the editor ended, or it had been edited less than 30 seconds before the crash and no snapshot existed yet. |
| The log says Another editor has the project's autosave folder open | A second editor has the same project open. Only the editor that owns the project autosaves. |
| Recovery is offered after every start | You chose Decide Later. Choose Recover or Discard for each document. |
| The editor crashes again right after recovery | Choose Safe Mode, or turn on Don't reopen last session's documents, then recover the documents one at a time. |