-
-
Notifications
You must be signed in to change notification settings - Fork 169
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 window updates very laggy (~1s between updates) #4365
Comments
Looks like you would be better off with
Try to enable this one. This can make massive difference to display performance.
vscode specifically: Now I've enabled opengl on the client, and rstudio and atom are definitely more responsive when typing (newlines still cause hiccups, but I guess that's fine). : #2248 (comment) Oh, and just in case this is caused by opengl rendering server-side (I have no idea how electron apps do their rendering). Try launching |
Thanks! Missed that as it appears to be missing in the manpage.
Tried it but saw no difference. Most likely because OpenGL is not available on my client though, the splash mentioned opengl failure. While it might help mitigate the symptoms I suspect the cause is elsewhere (see below).
Tried deleting the fallback rule and changing it to
It did show up instantly. Interestingly enough, running VSCodium "full screen" (as in one window covering most of the nested X server) within Xephyr (to get some drawing indirection) and firejail (for Xephyr convenience), using the same DPI settings, produced a smooth experience, albeit with compression artifacts. Now that I see it, I believe I might have had that experience a while ago on an earlier version. Does this ring enough bells or should I try to repro+bisect the server side?
|
Added in 37b1d13
It should be available pretty much everywhere.
What failure?
That would be way down the list of things to try. See https://github.com/Xpra-org/xpra/wiki/Reporting-Bugs |
tl;dr:
Changes nothing, full initial log:
(
info.txt, opened Firefox for reference Surprisingly enough, ChatGPT of all things suggested Side note: This is missing in the man page again. Would it make sense to generate the man page programmatically? (Or kill it completely to force users into the up-to-date Thanks for your help @totaam! I now have a workaround that seems to completely solve my particular problem, feel free to either close this or leave it open to track the potential heuristic improvement that could make this manual setting obsolete. If more info is needed on this or me verifying a fix would help, let me know. |
That's your distro package missing the accelerate extension, not ideal, but not that big of an issue.
Is this some kind of VM?
That's odd. $ python ./xpra/platform/gui.py | grep refresh-rate
- refresh-rate : 59996 What do you get on the client? |
yes, see initial description:
|
Looks like a bug in Xephyr.
My guess is that vscode uses the |
There seems to be a default of 50Hz in the xpra code. |
IIRC, we already clamp the refresh rate, which is why you get 1Hz rather than 0Hz. |
Describe the bug
VSCodium window updates are very laggy in an environment with direct 1 GBit/s ethernet where all other windows work just fine.
To Reproduce
Steps to reproduce the behavior:
xpra --dbus-launch= --dbus-control=no --ssh='ssh -o BatchMode=yes' --start-child='bash -c "xrdb -merge <(echo Xft.dpi: 120) ; tmux kill-server ; tmux start-server"' --opengl=no --webcam=no --pulseaudio=no --audio=no --av-sync=no --keyboard-sync=no --notifications=no --xsettings=no --bell=no --open-files=no --open-url=no --splash=no --forward-xdg-open=off --speaker=disabled --title='@title@ (remote)' start ssh://XXXXX@192.168.XXX.XXX/42
System Information (please complete the following information):
Additional context
Tried adding
--encoding=no-scroll
,--encoding=stream
, removing the DPI part,codium --disable-gpu
, VSCodium light theme, VSCode (not -ium) => no changes.Observed delay between updates is circa 1 second.
Client runs inside firejail+Xephyr but that doesn't appear to be a problem as all other windows work very well.
Does this sound like an xpra / encoding problem or more likely something on VSCodium side? I think NixOS / packaging is unlikely when all other windows run smoothly?
The text was updated successfully, but these errors were encountered: