mirror of
https://github.com/jetkvm/kvm.git
synced 2026-03-02 22:58:00 -05:00
Full screen performance issues on Chrome/Brave on Linux #2
Labels
No labels
component/keyboard-layout
component: cloud
component: device screen
component: extensions
component: hid/keyboard
component: hid/mouse
component: network
component: timesync
component: ui
component: updater
component: usb
component: usb/hid
component: usb/storage
component: video
component: webrtc
component: webserver
need-more-details
status: working-in-progress
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/kvm#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dlcasto on GitHub (Nov 8, 2024).
Fullscreen performance on Chrome/Brave on Linux is laggy enough that it can temporarily cause the screen to stop refreshing. Sometimes I have had to exit out of full screen mode, refresh the page, and then go back to full screen mode.
Although I have discovered that mashing the keyboard can get the screen to refresh while still in full screen mode.
Interestingly, it seems like the lag is worse when typing in fields on a web browser (rather than a text editor) on the machine I am controlling while in full screen mode. I don't have the performance issue when it's not in full screen mode on Chrome/Brave.
Firefox on the other hand, seems to handle full screen much better and without performance issues.
I've attached a quick screen capture showing typing, and then nothing responds on the screen until I start mashing keys.
screen-capture.zip
@lbayerlein commented on GitHub (Jan 9, 2025):
+1
@lsanderson commented on GitHub (Jan 9, 2025):
+1 here to brave/chrome on linux. And seeing it in full screen mode on Safari on Mac also. No problem in Firefox on either platform.
@IDisposable commented on GitHub (Oct 3, 2025):
Has this improved @dlcasto @lbayerlein @lsanderson