-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vscodium 1.85.2.24019+ extremely slow startup time #1823
Comments
Which aur are you using? |
I tried newest versions of both |
Came here to say that I encounter the same behavior with Arch+Gnome+Wayland.
|
same here on both of aur and flatpak |
Same here, was hoping latest version would fix it, but no. VSCode proper does not have the same issue. I am on Windows 10, using the "portable" version of VSCodium, without any nasty installers. |
Also experiencing this issue on Arch & Wayland |
Also facing this issue. Its happening to all electron based softwares( like obsidian) |
SUMMARY:removing full read:I have an interesting update that seem to be related to the issue.
Any wgpu program I tried to run would start with a significant delay and throw aforementioned errors. (I was surprised to learn To other users facing this issue:Please see if following similar steps fixes the issue and comment, so that this issue can be closed! |
It might also be another issue: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10257 I am seeing a lots of |
I've also been having this issue, I've tried every AUR package, and they're all the same, many minutes to open if at all. I have an Intel Arc A380 as my primary GPU and output, and an Nvidia RTX 3090 as my secondary GPU with no output, using prime offloading for individual programs and games, but not for my Wayland compositor (Hyprland) EDIT: I also weirdly found that in Wayland mode the secondary sidebar does not work, I can't drag to it, and if something was dragged to it in X11 mode it will be empty in Wayland mode. I just switched to X11 (Xwayland) and it starts instantly and works without issue. |
https://bbs.archlinux.org/viewtopic.php?id=298254 This fixed my error |
At some point between 1.85.2.24019 and 1.86.2.24053 vscodium got abnormally slow to startup
To Reproduce
1.85.2.24019
or below and runtime vscodium --verbose --disable-extensions
, CTRL-C when window loaded1.86.2.24053
or above and runtime vscodium --verbose --disable-extensions
, CTRL-C when window loadedExpected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop environment:
Additional context
The startup times from past recent versions:
(accurate to +/- 1 second as manually stopped with CTRL+C when everything loads)
logs from
1.87.0
logs from
1.85.0
Any idea what might have caused it, how to diagnose it further?
Is it specific to my setup or was something introduced across those versions that slows down the startup?
The text was updated successfully, but these errors were encountered: