This appeared out of nowhere. I think I accidentally cmd-clicked on an object property which would normally take me to the place where that property is defined. It might have happened quite soon after opening a file as it was a random, accidental click while trying to find something completely different. I was unable to replicate this with other already opened files, so perhaps some race condition...?
javascript
ide-typescript
Atom: 1.29.0-beta2 x64
Electron: 2.0.5
OS: Mac OS X 10.13.6
Thrown From: Atom Core
Uncaught TypeError: Cannot read property 'parseTextBufferSync' of null
At /Applications/Atom Beta.app/Contents/Resources/app/src/tree-sitter-language-mode.js:55
TypeError: Cannot read property 'parseTextBufferSync' of null
at TreeSitterLanguageMode.ensureParseTree (/Applications/Atom Beta.app/Contents/Resources/app/src/tree-sitter-language-mode.js:55:37)
at TreeSitterLanguageMode.buildHighlightIterator (/Applications/Atom Beta.app/Contents/Resources/app/src/tree-sitter-language-mode.js:120:16)
at ScreenLineBuilder.buildScreenLines (/Applications/Atom Beta.app/Contents/Resources/app/node_modules/text-buffer/lib/screen-line-builder.js:33:76)
at DisplayLayer.getScreenLines (/Applications/Atom Beta.app/Contents/Resources/app/node_modules/text-buffer/lib/display-layer.js:643:41)
at TextEditorComponent.queryScreenLinesToRender (/Applications/Atom Beta.app/Contents/Resources/app/src/text-editor-component.js:873:57)
at TextEditorComponent.updateSyncBeforeMeasuringContent (/Applications/Atom Beta.app/Contents/Resources/app/src/text-editor-component.js:385:16)
at TextEditorComponent.updateSync (/Applications/Atom Beta.app/Contents/Resources/app/src/text-editor-component.js:275:16)
at etch.getScheduler.updateDocument (/Applications/Atom Beta.app/Contents/Resources/app/src/text-editor-component.js:225:46)
at ViewRegistry.performDocumentUpdate (/Applications/Atom Beta.app/Contents/Resources/app/src/view-registry.js:238:13)
2x -1:13.9.0 core:save (input.hidden-input)
-1:00.4.0 core:close (input.hidden-input)
-0:59 core:save (input.hidden-input)
atom-chai-snippets 0.3.0
atom-ide-debugger-node 0.7.1
atom-ide-ui 0.12.0
atom-material-syntax 1.0.8
atom-material-ui 2.1.3
atom-ternjs 0.18.3
autocomplete-json 5.5.2
autocomplete-modules 2.1.0
autocomplete-sql 0.5.0
ava 0.11.0
base16-syntax 1.8.1
blame 1.0.1
build 0.70.0
build-dockerfile 1.0.1
build-make 0.13.0
color-picker 2.3.0
data-atom 0.29.0
docblockr 0.13.7
editorconfig 2.2.2
file-icons 2.1.22
firestore-rules-grammar 0.4.0
git-plus 8.0.0
git-projects 1.17.0
github-user-datatip 0.3.2
go-debug 1.6.2
go-plus 5.8.3
gruvbox-plus-syntax 1.3.1
highlight-selected 0.14.0
ide-bash 1.0.11
ide-css 0.3.0
ide-docker 0.0.2
ide-go 0.7.0
ide-json 0.2.1
ide-typescript 0.7.6
ide-yaml 0.4.3
indent-guide-improved 1.4.13
js-hyperclick 1.13.0
language-babel 2.85.0
language-diff 0.7.0
language-docker 1.1.8
language-dotenv 1.1.1
language-gitignore 0.3.0
language-graphql 0.10.1
language-ini 1.20.0
language-terraform 0.8.1
linter-coverage 0.2.0
linter-eslint 8.4.1
linter-markdown 5.2.2
linter-package-json-validator 2.0.0
linter-shellcheck 1.4.7
linter-swagger 0.4.2
linter-terraform-syntax 1.2.4
linter-travis-lint 1.0.1
minimap 4.29.8
minimap-cursorline 0.2.0
minimap-git-diff 4.3.1
minimap-linter 2.1.3
pretty-json 2.0.1
sort-lines 0.18.0
standardjs-snippets 2.6.2
sync-settings 0.8.6
teletype 0.13.3
todo-show 2.3.0
tree-view-autoresize 2.3.0
Thanks for the report!
I think I accidentally cmd-clicked on an object property which would normally take me to the place where that property is defined. It might have happened quite soon after opening a file as it was a random, accidental click while trying to find something completely different.
Sounds like it's not easily reproducible but thanks for these details too 馃憤 We can keep this open for a bit in case someone else runs into it and I'll try to reproduce when I can.
Tentatively tagged as tree-sitter based on the stack trace.
Thanks for the report! This whole ensureParseTree
code path has already been removed as part of https://github.com/atom/atom/pull/17551. This change will ship in Atom 1.30.
So I'm going to optimistically close this out, but we can definitely reopen if this problem occurs again after that release is out.
This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!
Most helpful comment
Thanks for the report! This whole
ensureParseTree
code path has already been removed as part of https://github.com/atom/atom/pull/17551. This change will ship in Atom 1.30.So I'm going to optimistically close this out, but we can definitely reopen if this problem occurs again after that release is out.