Atom 1.28.0 – haml files crash the editor

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn’t already filed: https://github.com/issues?utf8=✓&q=is%%3Aissue+user%%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

I’ve been seeing intermittent crashes. When atom crashes, I end up having to clear the window state to get it back (it crashes on start until that).

Steps to Reproduce

1. Open atom
2. Open several (somewhere between 5 and 8) haml files

Expected behavior: Atom is stable

Actual behavior: Atom crashes

Reproduces how often:
I can reproduce this 100%% of the time. Immediately after a crash, atom crashes on launch in safe mode or normal mode until I clear the window state.

Versions

You can get this information from copy and pasting the output of atom --version and apm --version from the command line. Also, please include the OS and what version of the OS you’re running.

My full settings: https://gist.github.com/calebmeyer/57593e1d220fef2910e3d881852a04b3

Additional Information

Because the crash happens so infrequently (about once every 2-5 hours), I’ve only reproduced it for my main work project, which is a ruby and rails app (single top level git folder).

Atom has only started crashing this way since I installed 1.28.0 (stable)

When it crashes, I only rarely get an actual crash dump. I’ll email you the crash logs.

I tried debugging in visual studio, and it was usually corrupted heap errors

This will occasionally occur when I try to open a new file by double clicking it from the tree-view. I’m not sure if that’s coincidence, but it’s happened a few times (different files each time)