Uncaught TypeError: Cannot set property '<~>' of null

[natecox]

Happened totally randomly.

Atom Version: 1.0.0 System: Mac OS X 10.10.3 Thrown From: project-ring package, v0.32.1

Stack Trace

Uncaught TypeError: Cannot set property '<~>' of null

At /Users/nate/.atom/packages/project-ring/lib/project-ring.coffee:249

TypeError: Cannot set property '<~>' of null
  at Object.module.exports.setProjectState (/Users/nate/.atom/packages/project-ring/lib/project-ring.coffee:249:3)
  at Object.module.exports.loadProjectRing (/Users/nate/.atom/packages/project-ring/lib/project-ring.coffee:348:4)
  at Object.module.exports.setProjectRing (/Users/nate/.atom/packages/project-ring/lib/project-ring.coffee:284:4)
  at FSWatcher.<anonymous> (/Users/nate/.atom/packages/project-ring/lib/project-ring.coffee:268:6)
  at emitTwo (events.js:87:13)
  at FSWatcher.emit (events.js:169:7)
  at FSEvent.FSWatcher._handle.onchange (fs.js:1215:12)

Commands

     -2:47.1.0 vim-mode:move-up (atom-text-editor.editor.vim-mode.command-mode.is-focused)
  2x -2:46.8.0 vim-mode:yank (atom-text-editor.editor.vim-mode.command-mode.is-focused)
  2x -2:43.2.0 blur (atom-text-editor.editor.vim-mode.is-focused.command-mode)
  2x -2:25.4.0 vim-mode:activate-characterwise-visual-mode (atom-text-editor.editor.vim-mode.command-mode.is-focused)
     -2:23.8.0 vim-mode:reset-command-mode (atom-text-editor.editor.vim-mode.is-focused.command-mode)
     -2:23.7.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.is-focused.command-mode)
     -2:23.5.0 vim-mode:move-up (atom-text-editor.editor.vim-mode.is-focused.command-mode)
     -2:22.6.0 vim-mode:activate-linewise-visual-mode (atom-text-editor.editor.vim-mode.is-focused.command-mode)
     -2:21.5.0 core:copy (atom-text-editor.editor.vim-mode.is-focused.visual-mode)
  2x -2:20.3.0 blur (atom-text-editor.editor.vim-mode.is-focused.visual-mode)
     -2:05.9.0 vim-mode:search (atom-text-editor.editor.vim-mode.visual-mode.is-focused)
     -2:05.9.0 blur (atom-text-editor.editor.vim-mode.visual-mode.is-focused)
     -2:05.1.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  2x -2:05.1.0 blur (atom-text-editor.editor.mini.is-focused)
     -2:03.6.0 vim-mode:activate-command-mode (atom-text-editor.editor.vim-mode.visual-mode.is-focused)
  4x -2:01.8.0 blur (atom-text-editor.editor.vim-mode.is-focused.command-mode)

Config

{
  "core": {
    "themes": [
      "isotope-ui",
      "one-dark-syntax"
    ],
    "disabledPackages": [
      "meteor-api",
      "meteor-helper"
    ]
  },
  "project-ring": {}
}

Installed Packages

# User
Stylus, v1.0.0
advanced-new-file, v0.4.3
angularjs, v0.3.0
atom-beautify, v0.28.7
color-picker, v2.0.7
ember-cli-helper, v0.7.2
ember-snippets, v1.4.0
emmet, v2.3.12
ex-mode, v0.5.1
file-types, v0.4.1
isotope-ui, v2.4.2
language-ember-htmlbars, v0.3.0
language-spacebars, v0.2.2
linter, v1.1.0
linter-coffeelint, v0.3.2
linter-haml, v0.4.0
linter-htmlhint, v0.0.17
linter-js-yaml, v1.1.1
linter-jshint, v0.1.7
linter-pep8, v0.2.0
linter-stylint, v2.0.0
markdown-preview-plus, v1.5.0
method-separator, v0.1.3
minimap, vundefined
project-ring, v0.32.1
vim-mode, v0.54.0
vim-surround, v0.7.2

# Dev
No dev packages

[vellerefond]

This is really strange and I cannot reproduce it even by playing around with several projects open, in different windows. I have placed more checks so as to avoid the null state being written to file. But the only time this could happen (the only time I can think of and it would be a debugging nightmare if it were true), would be during the opening of a project in a new window while other projects write to the configuration file. Could you please update to version v0.32.3 and report back whether this happens again?

Thank you very much for your time.