Polling exits itself

[Arcanemagus]

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: http://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

The @atom/watcher used in the github package is exiting itself after only doing a small number of polls, before github even initializes the watcher enough to log it has started.

Steps to Reproduce

1. Set Atom's file system watcher core setting to Polling
2. Enable file system diagnostics to console in the github package's settings
3. Close Atom
4. Configure the environment variables for @atom/watcher's internal diagnostics:
   • Set WATCHER_LOG_MAIN to a file in a directory that exists
   • Set WATCHER_LOG_POLLING to a file in a directory that exists
5. Start Atom in Safe Mode to a very specific folder on a Dell Compellent network share
6. Observe only a few (4-21 observed) polls before the watcher is closed
7. Observe that the github package never actually logs that the fs watcher has initialized

Expected behavior:

Polling to continue working.

Actual behavior:

Polling stops itself very shortly after starting, complete logs can be found in this Gist:
https://gist.github.com/Arcanemagus/051699026c8266ff064eefeec91f8820

Reproduces how often:

100% of the time for this specific folder, very rarely for other folders on the same network share.

Versions

Atom    : 1.26.0-beta2
Electron: 1.7.11
Chrome  : 58.0.3029.110
Node    : 7.9.0
apm  1.19.0
npm  3.10.10
node 6.9.5 x64
atom 1.26.0-beta2
python 2.7.14
git 2.17.0.windows.1
visual studio 2015

Additional Information

This particular network share has caused several issues in the past, which is why I am using Polling in the first place.