this post was submitted on 10 Jul 2024
5 points (100.0% liked)

Visual Studio Code

160 readers
2 users here now

founded 4 years ago
MODERATORS
 

A few weeks ago, VSCode began to constantly recreate tabs. Notably, they are always considered to have been modified, so I have to confirm their closure.

I initially thought that the undermentioned log might be the cause:

2024-07-10 13:50:43.340 [error] Unhandled method getIdAtPosition: Error: Unhandled method getIdAtPosition
    at /home/RokeJulianLockhart/.vscode-insiders/extensions/visualstudioexptteam.intellicode-api-usage-examples-0.2.8/dist/extension.js:2:398068
    at re (/home/RokeJulianLockhart/.vscode-insiders/extensions/visualstudioexptteam.intellicode-api-usage-examples-0.2.8/dist/extension.js:2:398362)
    at /home/RokeJulianLockhart/.vscode-insiders/extensions/visualstudioexptteam.intellicode-api-usage-examples-0.2.8/dist/extension.js:2:393146
    at Immediate.<anonymous> (/home/RokeJulianLockhart/.vscode-insiders/extensions/visualstudioexptteam.intellicode-api-usage-examples-0.2.8/dist/extension.js:2:393166)
    at processImmediate (node:internal/timers:478:21)
    at process.topLevelDomainCallback (node:domain:160:15)
    at process.callbackTrampoline (node:internal/async_hooks:128:24)

...because another entry appeared to always occur each time I closed one of these tabs. However, it stopped appearing today, so I'm a loss for the cause.

The attached URI is this video, which depicts the reappearance of the tabs. The attached image depicts multiple entries of the aforementioned log.

top 1 comments
sorted by: hot top controversial new old
[–] [email protected] 2 points 3 months ago* (last edited 3 months ago)

I see these tabs sporadically, usually no more than one at a time. But because they happen rarely and irregularly I was never able to pin down the reason.

I've noticed it tends to happen when I have a new editor open without saving it as a file: VS Code, or an extension, will then (sometimes) create an Untitled tab with non-visible changes.

More rarely I see it happening when I'm editing a new markdown file, before saving it for the first time. I'm using the extensions markdownlint, Markdown PDF, and Markdown All in One. Bisect is a bit useless because I was never able to reliably replicate the issue.