search

microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
164.53k stars 29.4k forks source link

Only top-left quadrant of window drawn after display/resolution change #58608

Closed fiendish closed 5 years ago

fiendish commented 6 years ago

Issue Type: Bug

Problem happens usually when I've just plugged in external monitors (dual side-by-side Dell U2718Q connected via USBC-DisplayPort cables) and woken my laptop (MacBook Pro 15-inch, 2017) up from sleep. But I can also sometimes reproduce it when switching between maximum and scaled less than maximum screen resolutions in macOS (10.13.6) system preferences.

Problem manifests as only the top-left quadrant of the window being drawn and the rest being blank white (as shown here in images). As you can see, it also affects the bug reporting window.

screen shot 2018-09-13 at 10 24 46 am screen shot 2018-09-13 at 10 26 05 am

The problem fixes itself (the window fully paints) if I drag the window past the barrier between my displays and then back.

VS Code version: Code 1.27.1 (5944e81f3c46a3938a82c701f96d7a59b074cfdc, 2018-09-06T09:14:32.385Z) OS version: Darwin x64 17.7.0

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2800)| |GPU Status|2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled| |Load (avg)|1, 2, 2| |Memory (System)|16.00GB (1.11GB free)| |Process Argv|/Applications/Visual Studio Code.app/Contents/MacOS/Electron .| |Screen Reader|no| |VM|0%|
Extensions (17) Extension|Author (truncated)|Version ---|---|--- emojisense|bie|0.4.1 markdown-preview-github-styles|bie|0.1.3 vscode-svgviewer|css|1.4.6 vscode-markdownlint|Dav|0.20.0 jupyter|don|1.1.4 gitlens|eam|8.5.6 gc-excelviewer|Gra|2.1.26 nbpreviewer|jit|1.0.0 theme-dark-plus-contrast|k3a|0.1.101 rainbow-csv|mec|0.5.0 python|ms-|2018.8.0 rewrap|stk|1.9.1 vscode-gitmoji-snippets|thi|3.2.0 vscode-lua|tri|0.12.4 python-extended-snippets|tus|0.0.1 markdown-all-in-one|yzh|1.6.0 propertylist|zho|0.0.2 (1 theme extensions excluded)
bpasero commented 6 years ago

We are building exploration builds that use a much newer version of Electron (our UI framework). I wonder if this issue reproduces with one of these builds, could you try? Download:

fiendish commented 6 years ago

I am trying the exploration build now. So far so good, but if it happens again I'll report back.

bpasero commented 6 years ago

Ok please do

fiendish commented 6 years ago

I think I can pretty reliably confirm now that the exploration build does fix the problem after going back and forth between the different versions over several days.

bpasero commented 5 years ago

Closing this issue given that we plan to release VSCode stable early February with Electron 3.x. If you want to benefit from the fix already, consider to use our insiders version that already contains the fix: https://code.visualstudio.com/insiders/