You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
I tried newest versions of both vscodium-bin and vscodium (using yay), both shared the same long startup delay.
For looking up the performance of the older versions I used modified PKGBUILD of vscodium-bin
Came here to say that I encounter the same behavior with Arch+Gnome+Wayland.
After the latest update, both native Wayland and XWayland versions display slow startup ( more than 10 sec, while before it loaded instantaneously).
I also have this error in journalctl -b at every startup:
gnome-shell[1148]: value "nan" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
gnome-shell[1148]: value "nan" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
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: