Open sweettyler opened 4 years ago
for more information please refer "https://github.com/microsoft/vscode/issues/100889". I see no improvement with the latest version.
What happens when you run with --disable-extensions
?
@deepak1556 same blank window with "--disable-extensions".
Sorry for closing the other issue prematurely, this is indeed a different one.
Can you attach the output of code-insiders --verbose --disable-extensions
. Does this issue happen when opening any file ?
[pzha@h050018 ~/Downloads]$ ~/mytools/VSCode-linux-x64/bin/code-insiders --verbose --disable-extensions
Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank"
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-Message: Failed to load module "pk-gtk-module"
[314030:0625/173723.707528:ERROR:edidparser.cc(102)] Too short EDID data: manufacturer id
[main 2020-06-25T22:37:23.779Z] Starting VS Code
[main 2020-06-25T22:37:23.781Z] from: /NFS/ud1/home1/pzha/mytools/VSCode-linux-x64/resources/app
[main 2020-06-25T22:37:23.781Z] args: {
: [],
diff: false,
add: false,
goto: false,
'new-window': false,
'reuse-window': false,
wait: false,
help: false,
'list-extensions': false,
'show-versions': false,
version: false,
verbose: true,
status: false,
'prof-startup': false,
'disable-extensions': true,
'disable-gpu': false,
telemetry: false,
logExtensionHostCommunication: false,
'skip-release-notes': false,
'disable-restore-windows': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-crash-reporter': false,
'disable-user-env-probe': false,
'skip-add-to-recently-opened': false,
'unity-launch': false,
'open-url': false,
'file-write': false,
'file-chmod': false,
'driver-verbose': false,
force: false,
'do-not-sync': false,
trace: false,
'force-user-env': false,
'no-proxy-server': false,
nolazy: false,
'force-renderer-accessibility': false,
'ignore-certificate-errors': false,
'allow-insecure-localhost': false
}
[main 2020-06-25T22:37:23.782Z] Resolving machine identifier...
[main 2020-06-25T22:37:23.782Z] Resolved machine identifier: 9a5e7896846559b142b72f45936cec6a0fa799f7a76d8034404b39634fff71e0
[main 2020-06-25T22:37:23.800Z] [storage state.vscdb] open(/NFS/ud1/home1/pzha/.config/Code - Insiders/User/globalStorage/state.vscdb, retryOnBusy: true)
[main 2020-06-25T22:37:23.801Z] lifecycle (main): phase changed (value: 2)
[main 2020-06-25T22:37:23.801Z] windowsManager#open
[main 2020-06-25T22:37:23.802Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 264, y: 21, width: 1029, height: 727 }
[main 2020-06-25T22:37:23.802Z] window#validateWindowState: 1 monitor working area { x: 0, y: 0, width: 1372, height: 750 }
[main 2020-06-25T22:37:23.802Z] window#ctor: using window state { mode: 1, x: 264, y: 21, width: 1029, height: 727 }
[314052:0625/173723.848841:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
(electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false". It will change to be "true" in Electron 9. For more information please check https://github.com/electron/electron/issues/18397
[314030:0625/173723.955963:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[main 2020-06-25T22:37:24.015Z] Setting proxy to 'http://www-authproxy.statoil.net:80', bypassing '
I had no problem with a previously released insider version, which was released last Friday.
We updated the runtime from Electron 7 to Electron 8 since last friday, this certainly seems related to that. What is your OS version and what is your running environment (i-e) remote X11 ?
Can you now run with code-insiders --verbose --disable-extensions --disable-gpu
I see viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[pzha@h050018 ~/Downloads]$ ~/mytools/VSCode-linux-x64/bin/code-insiders --verbose --disable-extensions --disable-gpu
Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank"
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-Message: Failed to load module "pk-gtk-module"
[317019:0625/180303.093246:ERROR:edidparser.cc(102)] Too short EDID data: manufacturer id
[main 2020-06-25T23:03:03.165Z] Starting VS Code
[main 2020-06-25T23:03:03.167Z] from: /NFS/ud1/home1/pzha/mytools/VSCode-linux-x64/resources/app
[main 2020-06-25T23:03:03.167Z] args: {
: [],
diff: false,
add: false,
goto: false,
'new-window': false,
'reuse-window': false,
wait: false,
help: false,
'list-extensions': false,
'show-versions': false,
version: false,
verbose: true,
status: false,
'prof-startup': false,
'disable-extensions': true,
'disable-gpu': true,
telemetry: false,
logExtensionHostCommunication: false,
'skip-release-notes': false,
'disable-restore-windows': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-crash-reporter': false,
'disable-user-env-probe': false,
'skip-add-to-recently-opened': false,
'unity-launch': false,
'open-url': false,
'file-write': false,
'file-chmod': false,
'driver-verbose': false,
force: false,
'do-not-sync': false,
trace: false,
'force-user-env': false,
'no-proxy-server': false,
nolazy: false,
'force-renderer-accessibility': false,
'ignore-certificate-errors': false,
'allow-insecure-localhost': false
}
[main 2020-06-25T23:03:03.168Z] Resolving machine identifier...
[main 2020-06-25T23:03:03.168Z] Resolved machine identifier: 9a5e7896846559b142b72f45936cec6a0fa799f7a76d8034404b39634fff71e0
[main 2020-06-25T23:03:03.201Z] [storage state.vscdb] open(/NFS/ud1/home1/pzha/.config/Code - Insiders/User/globalStorage/state.vscdb, retryOnBusy: true)
[main 2020-06-25T23:03:03.201Z] lifecycle (main): phase changed (value: 2)
[main 2020-06-25T23:03:03.202Z] windowsManager#open
[main 2020-06-25T23:03:03.202Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 270, y: 21, width: 1038, height: 727 }
[main 2020-06-25T23:03:03.203Z] window#validateWindowState: 1 monitor working area { x: 0, y: 0, width: 1372, height: 750 }
[main 2020-06-25T23:03:03.203Z] window#ctor: using window state { mode: 1, x: 270, y: 21, width: 1038, height: 727 }
(electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false". It will change to be "true" in Electron 9. For more information please check https://github.com/electron/electron/issues/18397
[317019:0625/180303.352504:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[main 2020-06-25T23:03:03.418Z] Setting proxy to 'http://www-authproxy.statoil.net:80', bypassing '
Thanks! , can you also confirm OS version and what is your running environment (i-e) remote X11 ?
Please let me know if you need more info and also how to get those info.
Can you try running with code-insiders --disable-features="VizDisplayCompositor"
could you please confirm the option --disable-features="VizDisplayCompositor" ?
I got a warning:
[pzha@h050018 ~/Downloads]$ ~/mytools/VSCode-linux-x64/bin/code-insiders --disable-features="VizDisplayCompositor" Warning: 'disable-features' is not in the list of known options, but still passed to Electron/Chromium. [pzha@h050018 ~/Downloads]$
yes you can ignore the warning, the option is respected by the runtime not vscode.
so with the option --disable-features="VizDisplayCompositor", I still got a blank window.
BTW, are you sure Electron 8 works with RHEL 7?
it's CentOS, not RHEL exactly.
[pzha@h050018 ~/Downloads]$ cat /etc/redhat-release CentOS Linux release 7.4.1708 (Core)
This is mostly a gpu issue that got regressed with Electron 8, can you test with electron fiddle https://github.com/electron/fiddle/releases/tag/v0.15.1 , and load the following fiddle https://gist.github.com/deepak1556/5ecb1eb5a7dca08d2681ab18595f9a45
Please check if the exploration builds have the same issue https://az764295.vo.msecnd.net/exploration/11a6eed191de586f764270db328f9b57ef34c1de/code-exploration-1593069439.tar.gz , they run on Electron 9
1) the exploration builds have the same issue; 2) I'll try electron fiddle later and post the result.
@deepak1556 thank you for your effort.
@deepak1556 1) I don't have the root privileges so I installed the prm with command "rpm2cpio electron-fiddle-0.15.1-1.x86_64.rpm | cpio -idv". 2) when I simply ran "electron-fiddle", I got an error as follows:
[pzha@h050018 bin]$ electron-fiddle [330858:0625/195849.809361:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /NFS/ud1/home1/pzha/Downloads/usr/lib/electron-fiddle/chrome-sandbox is owned by root and has mode 4755. Trace/BPT trap (core dumped)
3) when I ran electron-fiddle with option --no-sandbox, I got a blank window (see attachment) and the following message:
[pzha@h050018 bin]$ electron-fiddle --no-sandbox Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank" Gtk-Message: Failed to load module "pk-gtk-module" Gtk-Message: Failed to load module "pk-gtk-module" Creating main window (electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false". It will change to be "true" in Electron 9. For more information please check https://github.com/electron/electron/issues/18397 Electron's autoUpdater does not support the 'linux' platform
4) As I just got a blank window I had no chance to do anything further.
Thanks for confirming, I am setting up CentOS on my vm to investigate further.
On my machine code-insiders, electron-fiddle and electron run fine.
[parallels@centos-7 Downloads]$ cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)
Can you describe your OS setup ? what is echo $DISPLAY
on your machine ?
1) on the machine I am running VScode "echo $DISPLAY" returns "localhost:17.0" 2) Not sure if the following detail matters: I actually login from another virtual machine (and using HP Remote Grapphics Software for Windows 10 to connect to this virtual machine) to the machine on which I am running VScode (but I always work in this way). The virtual machine is running "Red Hat Enterprise Linux Workstation release 6.10 (Santiago)" according to "/etc/redhat-release" and the other is running "CentOS Linux release 7.4.1708 (Core)", which is a bit older than yours. 3) Not quite sure what exactly you mean about my OS setup. Is there any command that I can get what you want? 4) Is it possible that in my system some libraries are missing, or too old to work with Electron 8.x?
Thanks for the details
I am actually login from another virtual machine to the machine on which I am running VScode (but I always work in this way). The virtual machine is running "Red Hat Enterprise Linux Workstation release 6.10 (Santiago)" according to "/etc/redhat-release" and the other is running "CentOS Linux release 7.4.1708 (Core)", which is a bit older than yours.
Yes this what I was asking for in https://github.com/microsoft/vscode/issues/101069#issuecomment-649860986 :)
There is a known chromium issue when running on remote machine https://bugs.chromium.org/p/chromium/issues/detail?id=1035803 , this should be potentially fixed in the version of our exploration builds https://github.com/microsoft/vscode/issues/101069#issuecomment-649871872 . But you don't see them fixed in the exploration builds right ?
Can you run code-exploration --verbose
.
1) what I got with exploration builds is also a blank window.
2) the following is the output with "--verbose" (not sure if there is any way to make them a better format):
[pzha@h050018 ~]$ ~/mytools/VSCode-linux-x64/bin/code-exploration --verbose
Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank"
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-Message: Failed to load module "pk-gtk-module"
[345770:0625/223928.345218:ERROR:edidparser.cc(102)] Too short EDID data: manufacturer id
[main 2020-06-26T03:39:28.408Z] Starting VS Code
[main 2020-06-26T03:39:28.409Z] from: /NFS/ud1/home1/pzha/mytools/VSCode-linux-x64/resources/app
[main 2020-06-26T03:39:28.409Z] args: {
: [],
diff: false,
add: false,
goto: false,
'new-window': false,
'reuse-window': false,
wait: false,
help: false,
'list-extensions': false,
'show-versions': false,
version: false,
verbose: true,
status: false,
'prof-startup': false,
'disable-extensions': false,
'disable-gpu': false,
telemetry: false,
logExtensionHostCommunication: false,
'skip-release-notes': false,
'disable-restore-windows': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-crash-reporter': false,
'disable-user-env-probe': false,
'skip-add-to-recently-opened': false,
'unity-launch': false,
'open-url': false,
'file-write': false,
'file-chmod': false,
'driver-verbose': false,
force: false,
'do-not-sync': false,
trace: false,
'force-user-env': false,
'no-proxy-server': false,
nolazy: false,
'force-renderer-accessibility': false,
'ignore-certificate-errors': false,
'allow-insecure-localhost': false
}
[main 2020-06-26T03:39:28.410Z] Resolving machine identifier...
[main 2020-06-26T03:39:28.410Z] Resolved machine identifier: e11c0fc70a73a5b0589fa8514cab8721f30f9d0f6dae7cfb9ab59ba30e30b3c1
[main 2020-06-26T03:39:28.430Z] [storage state.vscdb] open(/NFS/ud1/home1/pzha/.config/Code - Exploration/User/globalStorage/state.vscdb, retryOnBusy: true)
[main 2020-06-26T03:39:28.430Z] lifecycle (main): phase changed (value: 2)
[main 2020-06-26T03:39:28.431Z] windowsManager#open
[main 2020-06-26T03:39:28.432Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 188, y: 74, width: 1042, height: 740 }
[main 2020-06-26T03:39:28.432Z] window#validateWindowState: 1 monitor working area { x: 0, y: 0, width: 1397, height: 764 }
[main 2020-06-26T03:39:28.432Z] window#ctor: using window state { mode: 1, x: 188, y: 74, width: 1042, height: 740 }
[345795:0625/223928.455278:ERROR:viz_main_impl.cc(152)] Exiting GPU process due to errors during initialization
[345770:0625/223928.525861:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[main 2020-06-26T03:39:28.559Z] Setting proxy to 'http://www-authproxy.statoil.net:80', bypassing '
I have tried every insider version of VScode since I reported this issue. What I have observed is whenever VScode uses electron 8.x and chrome 81 (?) I always get a blank window after I launch VScode.This is also the case for the version 1.48 released today. If the electron is 7.x and chrome is 78 then I have no issue.
for the latest v1.4.8, the error message is a bit different:
=====================================================================
[pzha@h050017 self_learning]$ ~/mytools/VSCode-linux-x64/bin/code-insiders --verbose --disable-extensions
/NFS/ud1/home1/pzha/mytools/VSCode-linux-x64/bin/../code-insiders: /lib64/libdbus-1.so.3: no version information available (required by /NFS/ud1/home1/pzha/mytools/VSCode-linux-x64/bin/../code-insiders)
/NFS/ud1/home1/pzha/mytools/VSCode-linux-x64/code-insiders: /lib64/libdbus-1.so.3: no version information available (required by /NFS/ud1/home1/pzha/mytools/VSCode-linux-x64/code-insiders)
/NFS/ud1/home1/pzha/mytools/VSCode-linux-x64/code-insiders: /lib64/libdbus-1.so.3: no version information available (required by /NFS/ud1/home1/pzha/mytools/VSCode-linux-x64/code-insiders)
Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank"
[30521:0710/102946.802286:ERROR:edidparser.cc(102)] Too short EDID data: manufacturer id
/proc/self/exe: /lib64/libdbus-1.so.3: no version information available (required by /proc/self/exe)
[main 2020-07-10T15:29:46.870Z] Starting VS Code
[main 2020-07-10T15:29:46.871Z] from: /NFS/ud1/home1/pzha/mytools/VSCode-linux-x64/resources/app
[main 2020-07-10T15:29:46.871Z] args: {
: [],
diff: false,
add: false,
goto: false,
'new-window': false,
'reuse-window': false,
wait: false,
help: false,
'list-extensions': false,
'show-versions': false,
version: false,
verbose: true,
status: false,
'prof-startup': false,
'disable-extensions': true,
'disable-gpu': false,
telemetry: false,
logExtensionHostCommunication: false,
'skip-release-notes': false,
'disable-restore-windows': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-crash-reporter': false,
'disable-user-env-probe': false,
'skip-add-to-recently-opened': false,
'unity-launch': false,
'open-url': false,
'file-write': false,
'file-chmod': false,
'driver-verbose': false,
force: false,
'do-not-sync': false,
trace: false,
'force-user-env': false,
'open-devtools': false,
'no-proxy-server': false,
nolazy: false,
'force-renderer-accessibility': false,
'ignore-certificate-errors': false,
'allow-insecure-localhost': false
}
[main 2020-07-10T15:29:46.872Z] Resolving machine identifier...
[main 2020-07-10T15:29:46.872Z] Resolved machine identifier: 9a5e7896846559b142b72f45936cec6a0fa799f7a76d8034404b39634fff71e0
[main 2020-07-10T15:29:46.899Z] [storage state.vscdb] open(/NFS/ud1/home1/pzha/.config/Code - Insiders/User/globalStorage/state.vscdb, retryOnBusy: true)
[main 2020-07-10T15:29:46.899Z] lifecycle (main): phase changed (value: 2)
[main 2020-07-10T15:29:46.899Z] windowsManager#open
[main 2020-07-10T15:29:46.900Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 75, y: 31, width: 1258, height: 737 }
[main 2020-07-10T15:29:46.900Z] window#validateWindowState: 1 monitor working area { x: 0, y: 0, width: 1372, height: 772 }
[main 2020-07-10T15:29:46.901Z] window#ctor: using window state { mode: 1, x: 75, y: 31, width: 1258, height: 737 }
/proc/self/exe: /lib64/libdbus-1.so.3: no version information available (required by /proc/self/exe)
[30543:0710/102946.939429:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
/proc/self/exe: /lib64/libdbus-1.so.3: no version information available (required by /proc/self/exe)
(electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false". It will change to be "true" in Electron 9. For more information please check https://github.com/electron/electron/issues/18397
[30521:0710/102947.053431:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[main 2020-07-10T15:29:47.100Z] Setting proxy to 'http://www-authproxy.statoil.net:80', bypassing '
@deepak1556 Has the fix of "#102011" been applied to the insider release today? I still have the blank window after the launch.
@sweettyler not yet, will update here once it has been released. Thanks!
@sweettyler please try the latest insiders and see if the issue continues to surface. Thanks!
@deepak1556 I tried "https://az764295.vo.msecnd.net/insider/eb1ca267d6a478734bd7f3d629ac9b80926ee9d1/code-insider-1595336839.tar.gz" and my problem is not solved. However, I am not sure if your fix has been included in this release or not. Maybe your meant to try tomorrow's release?
Thats the correct build with Electron 9 update. Reopening for further investigation.
Here is log:
========================================
[pzha@h050018 ~]$ ~/mytools/VSCode-linux-x64/bin/code-insiders --verbose --disable-extensions
Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank"
[283303:0721/162028.630697:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-Message: Failed to load module "pk-gtk-module"
[283303:0721/162028.702746:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id
[283328:0721/162028.707350:ERROR:appcenterapi.cc(52)] expecting appcenter url prefix
[main 2020-07-21T21:20:28.772Z] Starting VS Code
[main 2020-07-21T21:20:28.773Z] from: /NFS/ud1/home1/pzha/mytools/VSCode-linux-x64/resources/app
[main 2020-07-21T21:20:28.773Z] args: {
: [],
diff: false,
add: false,
goto: false,
'new-window': false,
'reuse-window': false,
wait: false,
help: false,
'list-extensions': false,
'show-versions': false,
version: false,
verbose: true,
status: false,
'prof-startup': false,
'disable-extensions': true,
'disable-gpu': false,
telemetry: false,
logExtensionHostCommunication: false,
'skip-release-notes': false,
'disable-restore-windows': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-crash-reporter': false,
'disable-user-env-probe': false,
'skip-add-to-recently-opened': false,
'unity-launch': false,
'open-url': false,
'file-write': false,
'file-chmod': false,
'driver-verbose': false,
force: false,
'do-not-sync': false,
trace: false,
'force-user-env': false,
'open-devtools': false,
'no-proxy-server': false,
nolazy: false,
'force-renderer-accessibility': false,
'ignore-certificate-errors': false,
'allow-insecure-localhost': false
}
[main 2020-07-21T21:20:28.774Z] Resolving machine identifier...
[main 2020-07-21T21:20:28.774Z] Resolved machine identifier: 9a5e7896846559b142b72f45936cec6a0fa799f7a76d8034404b39634fff71e0
[main 2020-07-21T21:20:28.795Z] [storage state.vscdb] open(/NFS/ud1/home1/pzha/.config/Code - Insiders/User/globalStorage/state.vscdb, retryOnBusy: true)
[main 2020-07-21T21:20:28.795Z] lifecycle (main): phase changed (value: 2)
[main 2020-07-21T21:20:28.796Z] windowsManager#open
[main 2020-07-21T21:20:28.796Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 25, y: 21, width: 1351, height: 761 }
[main 2020-07-21T21:20:28.797Z] window#validateWindowState: 1 monitor working area { x: 0, y: 0, width: 1397, height: 786 }
[main 2020-07-21T21:20:28.797Z] window#ctor: using window state { mode: 1, x: 25, y: 21, width: 1351, height: 761 }
[283328:0721/162028.807118:ERROR:viz_main_impl.cc(152)] Exiting GPU process due to errors during initialization
[283346:0721/162028.810857:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[283336:0721/162028.842465:ERROR:appcenter_api.cc(52)] expecting appcenter url prefix
[283303:0721/162028.886781:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[main 2020-07-21T21:20:28.925Z] Setting proxy to 'http://www-authproxy.statoil.net:80', bypassing '
If you need any other info please just let me know.
what happens when you start with --no-xshm
@deepak1556 with "--no-xshm" it WORKS!
do you need the log?
Thanks for confirming,
Chromium uses the following logic to decide whether to enable MIT-SHM https://source.chromium.org/chromium/chromium/src/+/master:ui/base/x/x11_shm_image_pool.cc;l=67-103, they recently added a patch to disable it for remote scenarios https://chromium-review.googlesource.com/c/chromium/src/+/2062900
Seems like the patch isn't working for CentOS, you should be able to repro the crash with chromium 83 or above as well. Can you report an issue with upstream so that it can fixed there. For now you will have to rely on the command line workaround.
@deepak1556 Thank you. Reported in https://bugs.chromium.org/p/chromium/issues/detail?id=1035803. Hopefully that's the right place.
Will run temporarily with "--no-xshm". Just curious why the versions based on Electron 7.3 + Chrome 78 works. Doesn't it use the shared memory?
thats because of feature improvement that made in after 78 https://bugs.chromium.org/p/chromium/issues/detail?id=991633
Just chiming in that this isn't just an issue on CentOS. I'm on Ubuntu 18.04 and I also got the blank/white screen behavior but only when ssh'ed into another Ubuntu box with X11 forwarding enabled (i.e. ssh -X somehost
; launch vscode on new hostand get blank screen).
Adding --no-xshm
also fixed it for me, so there's that.
Interestingly, running just $code always works. And, running $sudo code --user-data-dir [path] worked for a while initially on my Ubuntu 18.04. However, something happened recently and caused the blank white screen when running with sudo, but it works with the --no-xshm.
Just posting because I had a similar issue and fixed it...
Cause: Using a 4k display on the Xserver host with 200% scaling
I was having issues very similar to https://github.com/microsoft/vscode/issues/112335, as well as this one. X server host is Ubuntu 20.04, and running vscode within a local Docker container based on an Ubuntu 20.04 image. I was having issues with vscode having visual artifacts and crashing within a few seconds of starting.
My host laptop display is 4k (3840x2160), which I set to 200% scaling in order to make things legible. On a hunch I changed the resolution to 1920x1080 with 100% scaling and voila! vscode visual issues are gone and not crashing. Posting here in case it helps someone.
I am RDPing into a native Ubuntu 20.04 box and have this problem as well. I reverted to 1.48.2 based on this thread and it works so far (at least I can see the screen) but I haven't done much with it yet. (It doesn't load extensions, but I think that's a network/proxy issue...) Are there conclusive steps to take to get the latest version of vscode visible?
Just downloaded the latest version of VScode (https://az764295.vo.msecnd.net/insider/9b620b291e120caab8292cab38cad10c2b22dffe/code-insider-1593112949.tar.gz") and found it still shows a blank window after launch.