Editor crash

[Uplink03]

When I have go-debug installed my editor slows down during the day. At some point it stops responding and after a few minutes I get a dialogue box saying that the editor has crashed and if I want to reopen it.

If I remove go-debug Atom is very stable and usable. Any ideas on what's happening and where to look to get more info, please?

OS: Ubuntu 18.04 x86-64
Atom 1.28.0
go-debug 1.6.2

[lloiser]

You can try and change the "File System Watcher" in the settings to something else. It even says:

but may help prevent crashes or freezes.

So give it a try!
If it still fails and you really want to debug it try the following:

• start atom in development mode using atom --dev <folder>
• open the developer tools using the Toggle dev tools command from the command palette

You probably should see an error in there once atom crashes. A screenshot or copy/paste of it would be helpful.

[Uplink03]

I don't see any "File System Watcher" anywhere. The dev tools don't say anything either.

This is the only thing I get, all just leaving Atom idle with some Go code open and go-debug installed:

And that message doesn't say that Atom ran out of memory, but rather my computer somehow doesn't have enough to see why the crash happened (16 GB should be enough for everybody, right?). As far as I can tell though there's no memory leak.

Atom itself is still alive. It's just the editor that goes away, and the developer tools window says it lost its connection.

[lloiser]

Unfortunately I have no ubuntu available at the moment.

This "File System Watcher" is in the settings of atom itself (ctrl + , or via command palette Settings view: Open).
Here is a screen from a macOS machine:

Also checkout this text here:
https://flight-manual.atom.io/hacking-atom/sections/debugging/#find-crash-logs
Maybe this reveals some issues

Additionally have you searched the world wide web for this error message "Your computer does not have ......."? Maybe there are some smart people out there that already solved this problem...

[Uplink03]

Oh, that's where it was hiding. Thanks. I scrolled that page several times, but missed it each time. And using Control+F isn't an option in settings (that's something for the Atom team).

That memory message appears all over the place, so it's not very informative. Launchpad: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/718635

I found this file: /var/crash/_usr_share_atom_atom.1000.crash. It says it received a signal 11 (SEGV). If besides Electron it's all JavaScript, that's a bit strange.

I'll test if the File System Watcher settings make any difference.