Uncaught TypeError: Cannot read property 'length' of null about text-buffer

[izuzak]

@yongkangchen Can you reproduce this in safe mode?

[yongkangchen]

safe mode is normal. I guess this cause by autocomplete-plus, and I create the same issue.

[izuzak]

Thanks for confirming. I'm going to close this issue, but please reopen it in https://github.com/atom/atom if you notice it in safe mode.

Also, I'm going to cc @nathansobo and @benogle on this -- that stack trace above is interesting, it doesn't seem to include anything related to autocomplete-plus, so I'm wondering if there indeed is something we could do to prevent these exceptions.

[izuzak]

Reopening, see 94115e2#commitcomment-7727788

[zenizh]

Exactly the same problem here on OS X 10.9.4 and Atom 0.125.0.
And I also use autocomplete-plus.
Just for reference.

[yongkangchen]

@kami30k I temporary edit the file /Applications/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/marker.js and modify function resumeChangeEvents to avoid the annoying bug, and you can try it until they fix this.

    Marker.prototype.resumeChangeEvents = function() {
      var deferredChangeEvents, event, _i, _len, _results;
      deferredChangeEvents = this.deferredChangeEvents;
      this.deferredChangeEvents = null;
      _results = [];

      if(deferredChangeEvents){
        for (_i = 0, _len = deferredChangeEvents.length; _i < _len; _i++) {
          event = deferredChangeEvents[_i];
          this.emit('changed', event);
          _results.push(this.emitter.emit('did-change', event));
        }
      }
      return _results;
    };

[nathansobo]

This must be happening when something is inserting a marker within a buffer change event callback. Certainly a valid use case but it wasn't exercised by any of our code. This should be fixed on the next release, which we will expedite. Thanks for your patience.