{"action":"opened","issue":{"url":"https://api.github.com/repos/Microsoft/vscode/issues/55207","repository_url":"https://api.github.com/repos/Microsoft/vscode","labels_url":"https://api.github.com/repos/Microsoft/vscode/issues/55207/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/vscode/issues/55207/comments","events_url":"https://api.github.com/repos/Microsoft/vscode/issues/55207/events","html_url":"https://github.com/Microsoft/vscode/issues/55207","id":345074904,"node_id":"MDU6SXNzdWUzNDUwNzQ5MDQ=","number":55207,"title":"High gpu-process usage in 1.26.0-insider","user":{"login":"wayspurrchen","id":1059075,"node_id":"MDQ6VXNlcjEwNTkwNzU=","avatar_url":"https://avatars3.githubusercontent.com/u/1059075?v=4","gravatar_id":"","url":"https://api.github.com/users/wayspurrchen","html_url":"https://github.com/wayspurrchen","followers_url":"https://api.github.com/users/wayspurrchen/followers","following_url":"https://api.github.com/users/wayspurrchen/following{/other_user}","gists_url":"https://api.github.com/users/wayspurrchen/gists{/gist_id}","starred_url":"https://api.github.com/users/wayspurrchen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wayspurrchen/subscriptions","organizations_url":"https://api.github.com/users/wayspurrchen/orgs","repos_url":"https://api.github.com/users/wayspurrchen/repos","events_url":"https://api.github.com/users/wayspurrchen/events{/privacy}","received_events_url":"https://api.github.com/users/wayspurrchen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-27T03:07:47Z","updated_at":"2018-07-27T03:07:47Z","closed_at":null,"author_association":"NONE","body":"VSCode Insiders uses a significant amount of RAM for gpu-process on a fresh install. The screenshot shows 336 but I've seen it as high as 450 on a fresh start. If continuing development, will freeze after a short amount of time with the Windows 10 Reopen/Wait for process/Close prompt. Waiting long enough will unfreeze but performance is still poor.\r\n\r\n![image](https://user-images.githubusercontent.com/1059075/43299385-9e6d5fae-911f-11e8-8161-6e86a9268f2a.png)\r\n\r\nThis appears to be related to #36913 but wanted to highlight here that the latest version of insider (1.26.0-insider) does not appear to have fixed this issue for a fresh copy of Windows 10 Pro. I was able to avoid the issue in 1.25.0 by passing the `--disable-gpu` flag.\r\n\r\n- VSCode Version: 1.26.0-insider\r\n- OS Version: Windows 10 Pro\r\n\r\nCPUs | Intel(R) Core(TM) i7-8705G CPU @ 3.10GHz (8 x 3096)\r\n-- | --\r\nGPU Status | 2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: unavailable_off\r\nMemory (System) | 15.85GB (6.95GB free)\r\nProcess Argv | C:\\Program Files\\Microsoft VS Code Insiders\\Code - Insiders.exe\r\nScreen Reader | no\r\nVM | 0%\r\n\r\n\r\nSteps to Reproduce:\r\n\r\n1. Launch VSCode Insiders\r\n2. View Process Explorer\r\n\r\nDoes this issue occur when all extensions are disabled?: Yes"}}
{"actor":{"display_login":"wayspurrchen"}}