Autosaving stops working after map loaded from Autosave folder crashes (in V2.1.0)

[Maxxiii]

System Information

TrenchBroom V2.1.0

If map, loaded from Autosave folder crashes - autosaving stops working for the original map (which is outside of Autosave folder)

Steps to Reproduce

1. Create a map and save it as crashtest.map
2. Create a copy of this map in Autosave folder and rename it to crashtest.1.map (or wait for autosave)
3. Create another copy of this map in Autosave folder and rename it to crashtest.1-crash.map to emulate behavior when you open map directly from Autosave folder and it crashes, leaving this file. (or make it really crash somehow)
4. Open original map crashtest.map which is outside of Autosave folder
5. Wait for autosave to happen
6. Look in the console window
   There will be a red repeated error message "Aborting autosave" and autosave will no longer work.

Deleting crashed map file crashtest.1-crash.map solves this issue for TrenchBroom V2.1.0
Note, that there could be multiple crashes of map inside autosave folder (next one will generate crashtest.1-crash-1.map, then crashtest.1-crash-2.map etc), and they also affect autosave, so they all should be deleted to manually resolve this issue.

Crash-related log files (crashtest.1-crash.txt and crashtest.1-crash.log) doesn't make a difference on autosave feature, only -crash.map file.

Behavior reproduces for other sequential numbers too, like crashtest.2.map etc