Broken rendering after updated to 1.66.0
See original GitHub issueIssue Type: Bug
Not sure how to reproduce, but my VS Code instance becomes broken after updated to 1.66.0.
Texts are rendered in strange way. All of the menu, side bar, text editor, issue reporter and other components are affected.
VS Code version: Code 1.66.0 (e18005f0f1b33c29e81d732535d8c0e47cafb0b5, 2022-03-30T05:50:14.623Z) OS version: Windows_NT x64 10.0.19044 Restricted Mode: No
System Info
Item | Value |
---|---|
CPUs | Intel® Core™ i5-9400F CPU @ 2.90GHz (6 x 2904) |
GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
Load (avg) | undefined |
Memory (System) | 31.93GB (19.24GB free) |
Process Argv | –crash-reporter-id c37a94d8-788e-4c0d-b2a8-ce3c14d630e9 |
Screen Reader | no |
VM | 0% |
Extensions (16)
Extension | Author (truncated) | Version |
---|---|---|
project-manager | ale | 12.5.0 |
gitignore | cod | 0.7.0 |
vscode-eslint | dba | 2.2.2 |
git-extension-pack | don | 0.1.3 |
githistory | don | 0.6.19 |
xml | Dot | 2.5.1 |
gitlens | eam | 12.0.5 |
vscode-favorites | how | 1.10.2 |
rest-client | hum | 0.24.6 |
plantuml | jeb | 2.17.2 |
svn-scm | joh | 2.15.3 |
solidity | Jua | 0.0.137 |
vscode-language-pack-zh-hans | MS- | 1.66.1 |
vetur | oct | 0.35.0 |
scala | sca | 0.5.5 |
vscode-open-in-github | ziy | 1.3.6 |
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vstes627:30244334
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vsclayoutctrt:30451275
dsvsc009:30452663
pythonvsnew555:30457759
vscscmwlcmc:30438804
vscgsvid1:30447480
pynewfile477:30463512
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:11 (2 by maintainers)
Top Results From Across the Web
March 2022 (version 1.66) - Visual Studio Code
Learn what is new in the Visual Studio Code March 2022 Release (1.66) ... that this decision broke and we decided to revert...
Read more >Intrusive and non-intrusive containers - 1.66.0
In any case, new objects have to be created inside the container using ... and erasing objects since no memory management is done...
Read more >How to fix a Failed Render from After Effects - YouTube
5 things you can do so your videos will export.Failed Renders - it's so depressing when that happens. Adobe After Effects and Media...
Read more >VSCode 1.74.2 Download for Windows / Change Log ...
Safari not properly rendering Terminal after page reload ... VSCode 1.66.0 ... Latest update breaks due to proxy requirement.
Read more >App Manager Release Notes | Replicated Docs
Adds ability to deploy an application with new values after syncing ... Fixes an issue where trailing line breaks were removed during Helm...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think I solved my issue. Since this only happens when enabling GPU acceleration, I thought it might be related to NVIDIA control panel settings I changed. Turns out, long time ago I followed some Youtube video to enable Multi-Frame Sampled Antialiasing (MFAA). Once restore to the default
Off
, the issue is gone. Those who still has this problem could try restoring NVIDIA settings to default.Continuing the merged https://github.com/microsoft/vscode/issues/147982, here:
Still the same fog.
Appending
--disable-gpu
in the shortcut’s “Target” field fixes it.