The Wayback Machine - https://web.archive.org/web/20240823082605/https://github.com/atom/tree-view/issues/724
Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

TypeError: Cannot read property 'terminatePendingState' of undefined #724

Closed
Arcanemagus opened this issue Feb 10, 2016 · 2 comments · Fixed by #727
Closed

TypeError: Cannot read property 'terminatePendingState' of undefined #724

Arcanemagus opened this issue Feb 10, 2016 · 2 comments · Fixed by #727
Labels

Comments

@Arcanemagus
Copy link

  1. Open a project
  2. Double click on a file
  3. Before the first file has a chance to finish opening double click on a second file.

Note that I can only reproduce this on the first file opened in that session. Waiting for Atom to fully initialize before attempting to open the first file does not seem to affect the issue.

Atom Version: 1.6.0-beta0
System: Microsoft Windows 10 Enterprise
Thrown From: tree-view package, v0.201.0

Stack Trace

Uncaught TypeError: Cannot read property 'terminatePendingState' of undefined

At C:\Users\Landon Abney\AppData\Local\atom\app-1.6.0-beta0\resources\app.asar\node_modules\tree-view\lib\tree-view.js:473

TypeError: Cannot read property 'terminatePendingState' of undefined
    at TreeView.module.exports.TreeView.entryClicked (C:\Users\Landon Abney\AppData\Local\atom\app-1.6.0-beta0\resources\app.asar\node_modules\tree-view\lib\tree-view.js:473:68)
    at tree-view-file.<anonymous> (C:\Users\Landon Abney\AppData\Local\atom\app-1.6.0-beta0\resources\app.asar\node_modules\tree-view\lib\tree-view.js:183:26)
    at space-pen-div.jQuery.event.dispatch (C:\Users\Landon Abney\AppData\Local\atom\app-1.6.0-beta0\resources\app.asar\node_modules\jquery\dist\jquery.js:4435:9)
    at space-pen-div.elemData.handle (C:\Users\Landon Abney\AppData\Local\atom\app-1.6.0-beta0\resources\app.asar\node_modules\jquery\dist\jquery.js:4121:28)

Commands

Config

{
  "core": {
    "disabledPackages": [
      ".bin",
      "fast-eslint",
      "linter-flow",
      "atom-typescript",
      "markdown-preview-plus",
      "language-gfm",
      "git-control",
      "git-history",
      "linter-gjslint",
      "linter-htmlhint"
    ],
    "themes": [
      "seti-ui",
      "seti-syntax"
    ]
  }
}

Installed Packages

# User
atom-autocomplete-php, v0.18.7
autocomplete-python, v1.6.1
docblockr, v0.7.3
editorconfig, v1.2.4
file-watcher, v0.4.0
highlight-selected, v0.11.2
language-chef, v0.8.0
language-docker, v1.1.6
language-elixir, v0.10.1
language-haml, v0.23.15
language-ini, v1.14.0
language-markdown, v0.10.1
language-powershell, v2.1.0
language-r, v0.4.0
language-reg, v0.0.0
linter, v1.11.3
linter-alex, v2.0.0
linter-bootlint, v1.0.0
linter-coffeelint, v1.1.2
linter-csslint, v1.2.0
linter-docker, v0.1.2
linter-elixirc, v1.1.5
linter-erb, v1.0.2
linter-eslint, v6.0.0
linter-flake8, v1.10.1
linter-foodcritic, v0.5.2
linter-haml, v1.1.0
linter-javac, v1.5.0
linter-js-yaml, v1.2.5
linter-jscs, v3.4.5
linter-jshint, v1.3.0
linter-jsonlint, v1.1.5
linter-lintr, v1.0.4
linter-lua, v1.0.1
linter-markdown, v1.4.2
linter-pep8, v1.2.1
linter-perl, v0.7.2
linter-perlcritic, v0.3.1
linter-php, v1.1.8
linter-phpcs, v1.3.0
linter-phpmd, v1.4.1
linter-pylint, v1.2.0
linter-rails-best-practices, v0.2.2
linter-reek, v2.1.3
linter-rubocop, v0.4.7
linter-ruby, v1.2.1
linter-scss-lint, v2.5.1
linter-stylelint, v1.10.4
linter-tidy, v2.1.0
linter-tslint, v0.6.0
linter-ui-default, v0.0.2
mapfile-grammar, v0.1.0
minimap, v4.19.0
minimap-find-and-replace, v4.4.0
minimap-git-diff, v4.1.8
minimap-highlight-selected, v4.3.1
minimap-linter, v1.1.1
minimap-selection, v4.3.1
pigments, v0.23.1
seti-syntax, v0.4.1
seti-ui, v0.8.1
svn, v0.0.9
tab-control, v0.6.9
trailing-spaces, v0.3.2

# Dev
No dev packages
@50Wliu
Copy link
Contributor

50Wliu commented Feb 10, 2016

I believe I ran into this once yesterday when opening a file, realizing it was the wrong one, and almost immediately opening the next one down when Atom was first loading, which seems consistent to what @Arcanemagus reported.

Running Atom 1.6.0-dev-d091a10 on Windows 10 x64.

/cc @kuychaco

@50Wliu 50Wliu added the bug label Feb 10, 2016
@Arcanemagus
Copy link
Author

Btw, I was able to reproduce this once after the first file opened, so it definitely seems like an issue with the preview state being created, started to be turned into a full editor, then being destroyed by the new preview call before it is turned fully... but the call to terminatePendingState that still going through.

I'm just guessing here though 😛.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
2 participants