Workspace is erased when HDD is out of storage

[apclapp]

Summary

I have experienced an issue with Sublime where my projects become corrupted when I run out of disk space and close or switch projects. This is due to Sublime's project autosave functionality, which erases the .sublime-workspace file before attempting to save a new one (which it cannot due when there is no remaining disk space). This results in a corrupted Sublime project, where the .sublime-workspace file has been erased.

To be clear, I expect this is more of an issue on OS X, where there are some funny things that happen when the disk is running low on storage.

Expected behavior

Running out of disk space and closing sublime should not result in a corrupted workspace. If possible, Sublime should check for sufficient disk space before wiping the .sublime-project file.

Actual behavior

Running out of disk space and closing sublime (or switching projects) results in a zero-byte .sublime-workspace file, and a corrupted project/workspace.

Steps to reproduce

Have a project open in Sublime text, and let the system run out of disk space. Once disk space is exhausted, saving a file will result in an error saying there is space to save the file. That is expected, and is fine.

Attempt to close sublime, or change to another project. Upon doing so, Sublime will attempt to autosave the current project, but will report an error saying that there is not enough space on the disk to do so. (At this point, the .sublime-workspace file has been overwritten as zero-bytes)

Attempt to re-open the previous project, and sublime will report that the .sublime-workspace file is corrupted.

Environment

• Operating system and version:
  Mac OS X 10.12

• Sublime Text:

  • Build 3126