VSCodeVim / VSCodeVim/Vim

Failed to handle key `u`: TextEditor(vs.editor.ICodeEditor:1,$model12) has been disposed

Open
#7,523 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.21.10

Stack trace
DISPOSED: TextEditor(vs.editor.ICodeEditor:1,$model12) has been disposed
    at n (vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:8:1581)
    at Ja.$tryApplyEdits (vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2322:16900)
    at u._doInvokeHandler (vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1506:13116)
    at u._invokeHandler (vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1506:12800)
    at u._receiveRequest (vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1506:11462)
    at u._receiveOneMessage (vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1506:10140)
    at vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1506:8236
    at a.fire (vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:69:1712)
    at o.fire (vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:85:19631)
    at d._receiveMessage (vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:85:24212)
    at vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:85:21746
    at a.fire (vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:69:1712)
    at s.acceptChunk (vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:85:16459)
    at vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:85:15589
    at Socket.P (vscode-file://vscode-app/c:/Users/scornaz/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2984:8477)
    at Socket.emit (events.js:315:20)
    at addChunk (internal/streams/readable.js:309:12)
    at readableAddChunk (internal/streams/readable.js:284:9)
    at Socket.Readable.push (internal/streams/readable.js:223:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:188: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

Use the reported key u reproduction and the stack trace's $tryApplyEdits entry point to investigate why the TextEditor is disposed before the edit. Reproduce on VSCodeVim 1.21.10; done means the error no longer occurs when handling u.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
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.