Atom crashed and my source file ended up blank


#62

The issue itself aside – I find it equally unbelievable that someone would work without a VCS (or a simple backup solution) in 2017. Even more so for someone working with computers. This is 101 stuff.


#63

@idleberg While I agree with your points about VCS, let’s not forget that this issue is about Atom causing data loss. That still needs to be fixed and it shouldn’t matter whether someone is using VCS or not.


#64

I do use Git and have been since 2009. I just do not create WIP commits every 15 minutes. Thankfully my issues are gone after switching to a real text editor. The primary jobs of a text editor are typing and storing the content.


#65

That’s why I wrote β€œThe issue itself aside”


#66

I lost a week of work.

β€œBut your VCS and bla bla…”

Doesn’t matter. I’m not using Atom ever again…

Wish the best for the project.


#67

If everybody who experiences this very rare bug simply uninstalls, we will never figure out why it’s happening.

(I’ve had Atom crash multiple times and never lost anything except a little unsaved work that I should have saved.)


#68

I’m going to post this again: simply saying β€œI lost all my work” may be helpful for you to vent your frustration about something that shouldn’t be happening, but is not helpful in regards to Atom figuring out where the bug is.

So if you are interested in helping Atom pinpoint this bug so that it doesn’t happen to others, it would be very much appreciated if you could start by answering this set of questions.


#69

I’m sorry. Got too frustrated and the loss is causing me a lot of problems.

  1. What OS and version of the OS you’re running

Arch Linux kernel 4.11.5-pf

  1. Which version of Atom you have installed

1.21 (outdated atom-editor-bin AUR package)

  1. A list of all the packages you have installed along with their versions (you can get this easily with apm list)

Built-in Atom Packages (92)
β”œβ”€β”€ atom-dark-syntax@0.28.0
β”œβ”€β”€ atom-dark-ui@0.53.0
β”œβ”€β”€ atom-light-syntax@0.29.0
β”œβ”€β”€ atom-light-ui@0.46.0
β”œβ”€β”€ base16-tomorrow-dark-theme@1.5.0
β”œβ”€β”€ base16-tomorrow-light-theme@1.5.0
β”œβ”€β”€ one-dark-ui@1.10.8
β”œβ”€β”€ one-light-ui@1.10.8
β”œβ”€β”€ one-dark-syntax@1.8.0
β”œβ”€β”€ one-light-syntax@1.8.0
β”œβ”€β”€ solarized-dark-syntax@1.1.2
β”œβ”€β”€ solarized-light-syntax@1.1.2
β”œβ”€β”€ about@1.7.8
β”œβ”€β”€ archive-view@0.63.3
β”œβ”€β”€ autocomplete-atom-api@0.10.3
β”œβ”€β”€ autocomplete-css@0.17.3
β”œβ”€β”€ autocomplete-html@0.8.1
β”œβ”€β”€ autocomplete-plus@2.35.11
β”œβ”€β”€ autocomplete-snippets@1.11.1
β”œβ”€β”€ autoflow@0.29.0
β”œβ”€β”€ autosave@0.24.3
β”œβ”€β”€ background-tips@0.27.1
β”œβ”€β”€ bookmarks@0.44.4
β”œβ”€β”€ bracket-matcher@0.87.3
β”œβ”€β”€ command-palette@0.41.1
β”œβ”€β”€ dalek@0.2.1
β”œβ”€β”€ deprecation-cop@0.56.9
β”œβ”€β”€ dev-live-reload@0.47.1
β”œβ”€β”€ encoding-selector@0.23.5
β”œβ”€β”€ exception-reporting@0.41.4
β”œβ”€β”€ find-and-replace@0.212.2
β”œβ”€β”€ fuzzy-finder@1.5.9
β”œβ”€β”€ github@0.6.2
β”œβ”€β”€ git-diff@1.3.6
β”œβ”€β”€ go-to-line@0.32.1
β”œβ”€β”€ grammar-selector@0.49.5
β”œβ”€β”€ image-view@0.62.3
β”œβ”€β”€ incompatible-packages@0.27.3
β”œβ”€β”€ keybinding-resolver@0.38.0
β”œβ”€β”€ line-ending-selector@0.7.3
β”œβ”€β”€ link@0.31.3
β”œβ”€β”€ markdown-preview@0.159.15
β”œβ”€β”€ metrics@1.2.6
β”œβ”€β”€ notifications@0.69.2
β”œβ”€β”€ open-on-github@1.2.1
β”œβ”€β”€ package-generator@1.1.1
β”œβ”€β”€ settings-view@0.251.10
β”œβ”€β”€ snippets@1.1.5
β”œβ”€β”€ spell-check@0.72.2
β”œβ”€β”€ status-bar@1.8.13
β”œβ”€β”€ styleguide@0.49.7
β”œβ”€β”€ symbols-view@0.118.0
β”œβ”€β”€ tabs@0.107.2
β”œβ”€β”€ timecop@0.36.0
β”œβ”€β”€ tree-view@0.217.9
β”œβ”€β”€ update-package-dependencies@0.12.0
β”œβ”€β”€ welcome@0.36.5
β”œβ”€β”€ whitespace@0.37.3
β”œβ”€β”€ wrap-guide@0.40.2
β”œβ”€β”€ language-c@0.58.1
β”œβ”€β”€ language-clojure@0.22.4
β”œβ”€β”€ language-coffee-script@0.49.0
β”œβ”€β”€ language-csharp@0.14.2
β”œβ”€β”€ language-css@0.42.5
β”œβ”€β”€ language-gfm@0.90.1
β”œβ”€β”€ language-git@0.19.1
β”œβ”€β”€ language-go@0.44.2
β”œβ”€β”€ language-html@0.47.7
β”œβ”€β”€ language-hyperlink@0.16.2
β”œβ”€β”€ language-java@0.27.4
β”œβ”€β”€ language-javascript@0.127.3
β”œβ”€β”€ language-json@0.19.1
β”œβ”€β”€ language-less@0.33.0
β”œβ”€β”€ language-make@0.22.3
β”œβ”€β”€ language-mustache@0.14.1
β”œβ”€β”€ language-objective-c@0.15.1
β”œβ”€β”€ language-perl@0.37.0
β”œβ”€β”€ language-php@0.42.0
β”œβ”€β”€ language-property-list@0.9.1
β”œβ”€β”€ language-python@0.45.4
β”œβ”€β”€ language-ruby@0.71.3
β”œβ”€β”€ language-ruby-on-rails@0.25.2
β”œβ”€β”€ language-sass@0.61.1
β”œβ”€β”€ language-shellscript@0.25.3
β”œβ”€β”€ language-source@0.9.0
β”œβ”€β”€ language-sql@0.25.8
β”œβ”€β”€ language-text@0.7.3
β”œβ”€β”€ language-todo@0.29.2
β”œβ”€β”€ language-toml@0.18.1
β”œβ”€β”€ language-typescript@0.2.1
β”œβ”€β”€ language-xml@0.35.2
└── language-yaml@0.30.2

Community Packages (1) /home/vinicius/.atom/packages
└── rst-preview@1.3.1

  1. Your entire config.cson

β€œ*”:
core:
autoHideMenuBar: true
"exception-reporting":
userId: β€œ3a8a36ce-b015-4088-85e8-f805eebe825d”

  1. Your init.coffee

Don’t have it.

  1. Anything else you can think of that is relevant

On Windows 10, some months ago, it happened almost everyday for a week or two. In my case seems to me that it has something to do with returning from a system hibernation. For some reason the Atom instance can crash, and all opened files will get blanked. I could recover from VCS without many losses, then.

This time, same story, returned from hibernation on Linux and Atom crashed. Reopened it and all the files I was editing got blanked. It was terrible and for sanity’s sake I’m not using Atom until this bug is fixed.

The editor is great, though.


#70

Thanks very much! I understand how frustrating it is, because this occurred to me as well when Dell pushed an unstable BIOS update.

Regarding Windows hibernation, did Atom crash upon restoring from hibernation?


#71

Not recently. I noticed that this stopped happening and I can’t recall any other case after those I mentioned. Only happened on Linux this time.


#72

Signed up to update on this. I also experienced this about 3 times already. Lost some of my network configs. Going back to Sublime Text as well.


#74

What OS and version of the OS you’re running

Ubuntu 14.04

Which version of Atom you have installed

1.19.3

A list of all the packages you have installed along with their versions (you can get this easily with apm list)

Built-in Atom Packages (91)
β”œβ”€β”€ atom-dark-syntax@0.28.0
β”œβ”€β”€ atom-dark-ui@0.53.0
β”œβ”€β”€ atom-light-syntax@0.29.0
β”œβ”€β”€ atom-light-ui@0.46.0
β”œβ”€β”€ base16-tomorrow-dark-theme@1.5.0
β”œβ”€β”€ base16-tomorrow-light-theme@1.5.0
β”œβ”€β”€ one-dark-ui@1.10.5
β”œβ”€β”€ one-light-ui@1.10.5
β”œβ”€β”€ one-dark-syntax@1.7.1
β”œβ”€β”€ one-light-syntax@1.7.1
β”œβ”€β”€ solarized-dark-syntax@1.1.2
β”œβ”€β”€ solarized-light-syntax@1.1.2
β”œβ”€β”€ about@1.7.6
β”œβ”€β”€ archive-view@0.63.3
β”œβ”€β”€ autocomplete-atom-api@0.10.1
β”œβ”€β”€ autocomplete-css@0.16.2
β”œβ”€β”€ autocomplete-html@0.8.0
β”œβ”€β”€ autocomplete-plus@2.35.5
β”œβ”€β”€ autocomplete-snippets@1.11.0
β”œβ”€β”€ autoflow@0.29.0
β”œβ”€β”€ autosave@0.24.3
β”œβ”€β”€ background-tips@0.27.1
β”œβ”€β”€ bookmarks@0.44.4
β”œβ”€β”€ bracket-matcher@0.87.3
β”œβ”€β”€ command-palette@0.40.4
β”œβ”€β”€ dalek@0.2.1
β”œβ”€β”€ deprecation-cop@0.56.7
β”œβ”€β”€ dev-live-reload@0.47.1
β”œβ”€β”€ encoding-selector@0.23.4
β”œβ”€β”€ exception-reporting@0.41.4
β”œβ”€β”€ find-and-replace@0.208.3
β”œβ”€β”€ fuzzy-finder@1.5.8
β”œβ”€β”€ github@0.3.4-1
β”œβ”€β”€ git-diff@1.3.6
β”œβ”€β”€ go-to-line@0.32.1
β”œβ”€β”€ grammar-selector@0.49.5
β”œβ”€β”€ image-view@0.61.2
β”œβ”€β”€ incompatible-packages@0.27.3
β”œβ”€β”€ keybinding-resolver@0.38.0
β”œβ”€β”€ line-ending-selector@0.7.3
β”œβ”€β”€ link@0.31.3
β”œβ”€β”€ markdown-preview@0.159.12
β”œβ”€β”€ metrics@1.2.6
β”œβ”€β”€ notifications@0.67.2
β”œβ”€β”€ open-on-github@1.2.1
β”œβ”€β”€ package-generator@1.1.1
β”œβ”€β”€ settings-view@0.250.0
β”œβ”€β”€ snippets@1.1.4
β”œβ”€β”€ spell-check@0.71.4
β”œβ”€β”€ status-bar@1.8.11
β”œβ”€β”€ styleguide@0.49.6
β”œβ”€β”€ symbols-view@0.116.1
β”œβ”€β”€ tabs@0.107.0
β”œβ”€β”€ timecop@0.36.0
β”œβ”€β”€ tree-view@0.217.2
β”œβ”€β”€ update-package-dependencies@0.12.0
β”œβ”€β”€ welcome@0.36.4
β”œβ”€β”€ whitespace@0.37.2
β”œβ”€β”€ wrap-guide@0.40.2
β”œβ”€β”€ language-c@0.58.1
β”œβ”€β”€ language-clojure@0.22.3
β”œβ”€β”€ language-coffee-script@0.48.7
β”œβ”€β”€ language-csharp@0.14.2
β”œβ”€β”€ language-css@0.42.4
β”œβ”€β”€ language-gfm@0.89.1
β”œβ”€β”€ language-git@0.19.1
β”œβ”€β”€ language-go@0.44.1
β”œβ”€β”€ language-html@0.47.3
β”œβ”€β”€ language-hyperlink@0.16.1
β”œβ”€β”€ language-java@0.27.2
β”œβ”€β”€ language-javascript@0.126.1
β”œβ”€β”€ language-json@0.19.1
β”œβ”€β”€ language-less@0.32.0
β”œβ”€β”€ language-make@0.22.3
β”œβ”€β”€ language-mustache@0.14.1
β”œβ”€β”€ language-objective-c@0.15.1
β”œβ”€β”€ language-perl@0.37.0
β”œβ”€β”€ language-php@0.39.0
β”œβ”€β”€ language-property-list@0.9.1
β”œβ”€β”€ language-python@0.45.3
β”œβ”€β”€ language-ruby@0.71.1
β”œβ”€β”€ language-ruby-on-rails@0.25.2
β”œβ”€β”€ language-sass@0.59.0
β”œβ”€β”€ language-shellscript@0.25.1
β”œβ”€β”€ language-source@0.9.0
β”œβ”€β”€ language-sql@0.25.6
β”œβ”€β”€ language-text@0.7.3
β”œβ”€β”€ language-todo@0.29.1
β”œβ”€β”€ language-toml@0.18.1
β”œβ”€β”€ language-xml@0.35.1
└── language-yaml@0.30.0

Community Packages (6) /home/eghx/.atom/packages
β”œβ”€β”€ linter@2.2.0
β”œβ”€β”€ linter-spell@0.15.0
β”œβ”€β”€ markdown-pdf@2.1.0
β”œβ”€β”€ markdown-writer@2.7.3
β”œβ”€β”€ pdf-view@0.61.0 (disabled)
└── wordcount@2.10.4

Your entire config.cson

β€œ*”:
β€œatom-package-deps”:
ignored: [
β€œlinter”
]
core:
disabledPackages: [
β€œpdf-view”
]
telemetryConsent: β€œlimited"
themes: [
β€œone-light-ui”
β€œone-light-syntax”
]
editor:
fontSize: 13
"exception-reporting”:
userId: "43f87c83-786b-4fd8-93c8-77bc14fd4f66"
welcome:
showOnStartup: false
wordcount:
goal: 3039

Your init.coffee

β€˜β€™β€™

Your init script

Atom will evaluate this file each time a new window is opened. It is run

after packages are loaded/activated and after the previous editor state

has been restored.

An example hack to log to the console when each text editor is saved.

atom.workspace.observeTextEditors (editor) ->

editor.onDidSave ->

console.log β€œSaved! #{editor.getPath()}”

β€˜β€™β€™

Anything else you can think of that is relevant

I am always used to putting my system to sleep multiple times before I shut it down.

Atom got really slow at this point and I just closed it. On reopening I was shocked to see all the missing files. I hope you fix it. I see it has been around for over 2 years now. I also wrote a comment saying that this is ridiculous but then I deleted it, as Wiu pointed out it was useless.


#75

I found the file in .atom/recovery/ GOd BLESS! :slight_smile:


#76

If you have local-history installed, you can also right-click the file and select β€œShow history of current file”.

I strongly recommend anyone in this thread who has experienced this data-loss issue to install it. It keeps a bunch of timestamped backups of the files you’re working on, and allows you to go back in time to a previous version without the hassle of committing it to VCS. This would allow you to keep using Atom, knowing that if you’re hit by this bug again, you can always recover your work. As a side effect, it would allow you to keep using Atom, and contribute to this bug report whenever you’re hit with the bug again.


#77

Pretty basic stuff here!
No file editor should ever have an β€œAutomatically Save” feature without also automatically backing up the previously saved file (the back up does not need to be in the same working folder; backing up to ~/.atom/recovery seems fine).

My situation was that I was simply "cut"ting some code (that represented a day’s worth of work) to move in a little farther down in the page (I miss IntelliJ’s Option-Shift-Up/Down command to simply move the selected lines of code), and as Murphy would have it, my Mac froze the instant that I cut the code.
I think to myself β€œOh well, at least it didn’t have a chance to save the file!”.
Guess who was wrong.
My Mac rebooted and when Atom reloaded the file was missing the cut code and [to add insult to injury] shows that the file is unsaved!

I specifically did NOT want to save the file between the Cut-And-Paste.

Unacceptable in 2018 that I have to be paranoid about using the clipboard cut feature, and that an editor with an β€œAuto Save” fails in the nearly the worst expected way when a user cuts to the clipboard and the system immediately reboots.

It is enough for me to consider never using Atom ever again; I now have a reason to try out Visual Studio Code (which I realize could indeed have the same problem).


#78

Atom doesn’t have an autosave function built in. When it’s closed and reopened, it remembers unsaved files that were previously open. The fact that the file indicates that it was unsaved means that it didn’t get saved, so the file on your hard drive should have had the original code in it.


#79

the same happened to me right now :weary: lost all my work :sob:


#80

And if you provide the information LeeDohm asked for, your comment might contribute something to this thread.


#81

Yup. This just happened to me to. i’m using the Windows 10 Atom v1.24.0 x64 and Atom crashed, taking a file with him. When I reopened the file it was not 0 bytes, but all code was replaced with spaces.

And there was nothing inside my ~/.atom/recovery, saddly.


#82

Reporting that I had this issue as well and have lost about a week’s worth of work. Very surprised that this issue hasn’t been resolved yet.

I will be switching back to a stable IDE that doesn’t delete my work after a system reboot.