VSCodeVim / VSCodeVim/Vim

Failed to handle key `<Esc>`: TextEditor(vs.editor.ICodeEditor:1,$model2) has been disposed

Open
#8,225 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

VSCodeVim version: 1.24.3

Stack trace 
DISPOSED: TextEditor(vs.editor.ICodeEditor:1,$model2) has been disposed
    at i (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:10:1628)
    at Bl.$tryApplyEdits (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2703:18076)
    at v._doInvokeHandler (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1705:13079)
    at v._invokeHandler (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1705:12761)
    at v._receiveRequest (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1705:11531)
    at v._receiveOneMessage (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1705:10233)
    at vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1705:8340
    at b.invoke (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:82:145)
    at r.deliver (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:82:2266)
    at o.fire (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:82:1844)
    at a.fire (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:544:19267)
    at g._receiveMessage (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:544:23854)
    at vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:544:21388
    at b.invoke (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:82:145)
    at r.deliver (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:82:2266)
    at o.fire (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:82:1844)
    at o.acceptChunk (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:544:16098)
    at vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:544:15228
    at Socket.O (vscode-file://vscode-app/c:/Users/jwcha/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:3173:22267)
    at Socket.emit (node:events:390:28)
    at addChunk (node:internal/streams/readable:315:12)
    at readableAddChunk (node:internal/streams/readable:289:9)
    at Socket.Readable.push (node:internal/streams/readable:228:10)
    at Pipe.onStreamRead (node:internal/stream_base_commons:199:23)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report provides only placeholder reproduction steps and a stack trace from VSCodeVim 1.24.3. Start by reproducing the failure when pressing Esc and use the reported TextEditor disposal error to trace the responsible extension path. Done means pressing Esc no longer attempts to apply edits to a disposed editor.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.