vscode: Syntax Highlighting and Inlay Hints are broken

Type: Bug

I just noticed a very odd bug. In a TypeScript file, syntax highlighting got all messed up after scrolling up once:

2

After scrolling back down, everything is back to normal:

1

This error is repeatable. Scrolling further up above the point of breakage keeps everything broken. Scrolling further down below that point keeps everything highlighted correctly.

VS Code version: Code 1.71.1 (e7f30e38c5a4efafeec8ad52861eb772a9ee4dfb, 2022-09-08T19:41:12.369Z) OS version: Linux x64 5.15.0-47-generic snap Modes: Sandboxed: No

System Info
Item Value
CPUs 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz (8 x 4273)
GPU Status 2d_canvas: unavailable_software
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
opengl: disabled_off
rasterization: disabled_software
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software
webgpu: disabled_off
Load (avg) 1, 1, 1
Memory (System) 31.07GB (20.26GB free)
Process Argv –no-sandbox --force-user-env --new-window --crash-reporter-id 23d56de3-001d-431f-81e8-0c352e7ea82f
Screen Reader no
VM 0%
DESKTOP_SESSION ubuntu
XDG_CURRENT_DESKTOP Unity
XDG_SESSION_DESKTOP ubuntu
XDG_SESSION_TYPE x11
Extensions (56)
Extension Author (truncated) Version
codesnap adp 1.3.4
toggle-excluded-files eam 1.7.0
tsl-problem-matcher amo 0.6.2
vscode-zipfs arc 3.0.0
better-toml bun 0.3.2
vscode-eslint dba 2.2.6
gitlens eam 12.2.2
EditorConfig Edi 0.16.4
RunOnSave eme 0.2.0
json-tools eri 1.0.2
prettier-vscode esb 9.9.0
copilot Git 1.47.6882
vscode-pull-request-github Git 0.50.0
vscode-test-explorer hbe 2.21.1
rest-client hum 0.25.1
template-string-converter meg 0.6.0
git-graph mhu 1.30.0
compare-folders mos 0.22.3
vscode-json5 mrm 1.0.0
vscode-docker ms- 1.22.1
vscode-language-pack-de MS- 1.71.9140925
python ms- 2022.14.0
vscode-pylance ms- 2022.9.40
jupyter ms- 2022.8.1002431955
jupyter-keymap ms- 1.0.0
jupyter-renderers ms- 1.0.9
remote-containers ms- 0.251.0
remote-ssh ms- 0.84.0
remote-ssh-edit ms- 0.84.0
remote-wsl ms- 0.66.3
vscode-remote-extensionpack ms- 0.21.0
azure-account ms- 0.11.1
hexeditor ms- 1.9.8
live-server ms- 0.4.1
powershell ms- 2022.8.5
test-adapter-converter ms- 0.1.6
vscode-js-profile-flame ms- 1.0.4
hide-gitignored npx 1.1.0
vetur oct 0.36.0
vscode-jest Ort 4.6.0
vscode-twoslash-queries Ort 1.1.0
typescript-mono-repo-import-helper q 0.0.6
java red 1.10.0
vscode-sort-json ric 1.20.0
gitconfig sid 2.0.1
sort-lines Tyr 1.9.1
intellicode-api-usage-examples Vis 0.2.4
vscodeintellicode Vis 1.2.28
vscode-java-debug vsc 0.44.0
vscode-java-dependency vsc 0.21.0
vscode-java-pack vsc 0.25.2
vscode-java-test vsc 0.37.1
vscode-maven vsc 0.39.0
vscode-icons vsc 11.18.0
vscode-todo-highlight way 1.0.5
vitest-explorer Zix 0.2.29
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411cf:30557515
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
hb751961:30553087
dsvsc012:30540252
azure-dev_surveyone:30548225
i497e931:30553904
40g7c324:30573242

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16 (7 by maintainers)

Most upvoted comments

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

I’ll try next time it happens. I’m afraid though that reloading without extensions fixes the issue like restarting VSCode does, so I’d have to work in a window that’s unusable due to missing extensions until the issue happens again maybe.