Atom crashed and my source file ended up blank

Well, the file I was working on wasn’t edited by another process as far as I know. But as I mentioned, I was running it with Python The file was on my local C: drive which has plenty of space, although I’m pretty sure the heavy python script I was running overloaded my memory.

Were the two files open in Atom when your computer froze?

Yes, the two files were open. Although I’m not why both were blank since only one was being processed by Python.I should maybe also mention that after my computer froze I get the following error when starting atom:

“Failed to load config.cson”

And also it won’t detect python.exe even though it’s in my PATH.

Shit, just happened to me in a massive work file.
It was about 1m sizes file.
5 days work are lost.
PC restarted because power down. When i switched it on the last two files that i have worked on were blank.

Fuck this. Back to sublime.

Hi,

I have got the same problem, it has happened in multiple occasions. On my Mac and PC
saved files got wiped clean to 0 bytes

I am running 1.7.3

My secenario is:

I saved the file, then working on the next file.

Once i have too many tabs opened (7-10)

i did Save all file by clicking the the save all under the file menu

followed by a close all tabs

when i revisit couple of files i modified earlier its all empty. Some has been saved and some haven’t

I like the Editor, but I can’t justify it when it comes to lost of work

We’re taking this very seriously. Finding and fixing this is a high priority for us. We’ve been trying to reproduce this to no avail. We would like to try and replicate your environment. For that we’ll need:

  1. What OS and version of the OS you’re running
  2. Which version of Atom you have installed
  3. A list of all the packages you have installed along with their versions (you can get this easily with apm list)
  4. Your entire config.cson
  5. Your init.coffee
  6. Anything else you can think of that is relevant

We want to get to the bottom of this, so any help you can give us to replicate the problem would be sincerely appreciated!

1 Like

This happened to me and I lost a text note written for 3 month.

We’re taking this very seriously. Finding and fixing this is a high priority for us. We’ve been trying to reproduce this to no avail. We would like to try and replicate your environment. For that we’ll need:

  1. What OS and version of the OS you’re running
  2. Which version of Atom you have installed
  3. A list of all the packages you have installed along with their versions (you can get this easily with apm list)
  4. Your entire config.cson
  5. Your init.coffee
  6. Anything else you can think of that is relevant

We want to get to the bottom of this, so any help you can give us to replicate the problem would be sincerely appreciated!

This just happened to me, too. I lost about half a day’s work. I’ve lost that much work a couple of times because of a mistake that I made, but NEVER because my editor lost its mind. For perspective, I’ve been coding since 1985, and used a LOT of different editors in that time. I can’t recall the last time I used an editor that didn’t provide an automatic backup by default, but I’m sure it’s been at least twenty years, if not more. And I don’t think it was excusable even then.

I’ve been using Atom for about a month, and I really like it, but this was a deal-breaker for me.
To anyone suggesting git as a solution: Don’t be silly. Of course, any sane devs are using git or hg or some other VCS on everything, and making commits reasonably frequently. However, I don’t make meaningless commits every half hour out of fear that my tools will misbehave. I’m sure there are people that do this, but I haven’t met any. That’s certainly not the norm.

I wasn’t expecting anything like IntelliJ’s local history, but emacs has created an automatic file backup for at least the last 30 years. That should really be the bare minimum default behavior for any editor (and it is, in the many other editors I’ve used). If this isn’t the default behavior in Atom, it should have a huge warning in its start up screen that says: “WARNING: Atom may randomly delete your code! Please ensure that you keep regular backups constantly” Admittedly, that will scare some people off, but you’ll probably lose more users if their code gets deleted randomly. You lost me for sure.

I was using Atom 1.7.3 - working on a python file. I was using a handful of packages, including MagicPython and python-yapf.

That’s as detailed a bug report as I can give. I’ve already deleted my Atom config, and I’m not very motivated to restore it from a backup and put in the effort for an editor I’m not going to use any more. I just don’t have confidence in the dev team. I’m sure there are reasons why auto-backup isn’t the default, but I have trouble imagining that this was a good decision. For me, Atom doesn’t do the job so much better than the alternatives that I want to keep using it, wondering what other surprises await me.

Please understand that none if this is meant with any hostility or malice - If it seems harsh, please forgive me. I intend no insult. Personally, I always want to know why I’ve lost a user, so this is just meant as my perspective on the importance of providing at least one default automatic backup for every edited file. I hope my feedback is useful.

4 Likes

I find my problem is caused by the atom-beautify package. It only happens when I save the HTML code at the second time and the file has been tracked by git. After disabling atom-beautify, Atom no longer crashes on OS X 10.11.5. This cause is probably different from others.

I just had this happen to me, it was a SCSS File. I clicked save and went to view my browser… Styles broken, I go back to Atom and it has a notice that it has crashed and if I want to reload or close it …

File gone, overwritten by nothing…

This is 100% unacceptable, fortunately in my case it was a tiny file I can redo but this shouldn’t be an issue at all. It is getting harder and harder to take Atom seriously as a competent text editor.

This hasn’t happened to me since the backup option you gave (I know it shouldn’t be related), but I find it weird that it’s not enabled by default…

In any case, this problem happened for me on both Ubuntu 15 and Windows 10 and it has happened with several recent versions of Atom, but not the most recent (and I have the option turned on). I can also tell that this issue has happened on a pretty standard installation. I’m hopeful this configuration option will help me in the future and if not, I’ll report back to you with more details.

This just happened to me too, with version 1.8.0. I was connected to a cluster where my file was saved, the connection was lost and Atom froze, when I opened it again my file was blank. This is unacceptable, I won’t be using Atom any more.

I had the problem with SublimeText 2 in the past, when the disk is full i ended up with 0 KB files.

Yesterday again my disk was full (may employer bought a laptop with only 100 GB SSD) but i didn’t have the problem with Atom. :slight_smile:

Now Atom (1.8.0) crashed. 6 local files open, 2 unsaved. The saved ones are OK but the unsaved are lost. That should not happen. I will try out the local-history plugin.

A bugreport with this informations would not be very helpful.

Do you know if a crash report is written somewhere (OS X)?

Check Console.app.

Yes, there is a crash report. Thanks!

ReportCrash[30557]: Saved crash report for Atom Helper[10854] version 1.8.0 (1.8.0) to /Users/davidak/Library/Logs/DiagnosticReports/***

Just happened to me too!
First, the width of the page began jerking back and forth a few pixels, causing the long document I was writing to constantly reflow the text and run slowly. It seemed like there was something wrong with the Minimap plugin since if the minimap was not there, the editor window would have nothing to expand into / shrink from. So I turned off Minimap. Not sure if this was anything to do with what followed.

Around ten minutes later, while I was typing, the editor froze followed by my cursor and entire Windows machine and I had to force shutdown via the power button. Atom has done this before, but I always save frequently so I thought it would be fine. This time, however, I opened Atom and saw the entire file for a split second - after which it was all replaced by blanks. Then, being careful not to save, I opened the file in another text editor. The file’s contents on disk had been completely blanked.

Really bizarre, and extremely frustrating. Had to rewrite the entire thing from memory, in a different text editor of course.

In my experience these sorts of crashes always happen right in the middle of typing a word. Unfortunately that’s all the context I can give. This was the first time it actually modified the file on disk instead of just losing the unsaved work.

Hi @jdjakub, can you please answer @lee-dohm’s questions available here? Thanks!

Also, I would suggest that you update to the newly-released Atom 1.9.0. That version contains a new feature that should prevent these kinds of scenarios from happening again. In the event that Atom cannot automatically recover your files, they should be available at %USERPROFILE%\.atom\recovery.

Windows 8 x64
Atom v1.6.1
Happens to me too, I’ve lost hour of work with text file. Maybe this issue is out-of-date for the latest version, but, unfortunately, editor doesn’t suggests me any updates to the new version

The current version is 1.9.8. You may have to update manually.