I experience the exact same problem on Windows 10 after updating to Atom 1.6

But instead of using Nautilus (duh), I'm using "SFTP Net Drive Free" to mount a folder of a local virtual machine (Debian Jessie) as a network drive.

Should I open a separate issue because of the different OS?

same issue here on archlinux, mounting folder throught sshfs, it freezes as soon as I try to open a file (but I can browse directories)

I have a very similar problem, Atom 1.6 randomly freezes when working on files on a Samba share on Windows 10.
I attached a screenshot where you can clearly see that the editor basically stops responsing for about 10 seconds.

I traced the bottleneck to

relativizeToWorkingDirectory (_path) {
return this.getRepo()
.then(repo => this.relativize(_path, repo.workdir()))
}

in src/git-repository-async.js (line ~165), which eventually leads to

function _tickCallback() {
...
}

In node.js, line ~335, whose executions lasts about 10 seconds. It's making the editor unusable, because I work on Samba shares. Is there a way to downgrade to 1.5 while this is taken care of?

@dborsatto The download page for all versions of 1.5.4, the latest release without this issue, is at:
https://github.com/atom/atom/releases/tag/v1.5.4

I cannot speak for the Windows version, but in Ubuntu I was able to uninstall 1.6.0 (without purging settings) and reinstall 1.5.4 without any settings or plugin conflicts occurring, but mileage may vary.

I am having the exact same issue as described here on OSX El Capitan (10.11.3) using a SMB file share as source folder v.1.5.4 works without issue. Thanks @dborsatto for the v.1.5.4 link.

Confirmed, I am using 1.6.0 without any samba or sshfs shares and is doing the same thing. 1.6.0 is currently unusable.

I am having the same issue for SSHFS mounted folder. Previous release does not have this issue. This is happening on OSX El Capitan

I can confirm the same issue happening on Fedora 23 while working with SMB.

same problem on mac OS X Yosemite 10.10.5 - gone back to 1.5.4

I have the same issue on OS X 10.11.4 working on a remote git project (mounted using SSHFS 2.5.0 and OSXFUSE 2.8.3). This bug makes Atom unusable. If a fix is not available very soon, version 1.6.0 should be pulled.

@Rondo5000 could you change the title? The issue is not related to SFTP only, from what I can gather it happens with every kind of network directory (SFTP, Samba, SSHFS etc).

I work with a Ubuntu VM guest as a local server, using Windows 10 as a host, and until now I used Samba to share a folder from inside my VM (I work with symlinks so I can't use NTFS) so I could access it from the host. I knew of performance issues with Git, that's why I can't use a GUI (like SourceTree or the recent GitKraken) because of unreasonable loading times, so until now I've stuck with command line via SSH, or using Ungit (which gets executed inside the server).
Now it sounds like whatever Atom was doing, it was more performant under these circumstances. If they won't find a fix, I'll either have to stick with 1.5.4, or I'll have to start using Sublime (please please please don't make me do that).

Same issue here on OS X El Capitan using SSHFS and Fuse. As I only work with remote drives, this makes atom unusable...