mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #957] Cursor will stutter and lock up when there's too much data in the clipboard #767
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#767
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 @CorvusUrro on GitHub (Nov 23, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/957
When "Clipboard Sharing" is enabled and a large amount of data is in the clipboard (such as an image) the cursor will rapidly flick back and forth between the two devices, often being entirely unable to go to the other device at all.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Smooth transition to the other PC, or at the very least no locking up
Desktop (please complete the following information):
OS: Windows 10 and Linux Mint
Barrier version 2.3.3
Additional context
Identical to issue #775 which was closed due to inactivity without being reviewed but is still an issue so probably shouldn't be closed.
@chris-y commented on GitHub (Dec 8, 2020):
I am also seeing this issue. Server is a Raspberry Pi 4, when I have an image in the clipboard and I move over to another screen (in this case a Linux Mint laptop) it will occasionally completely freeze up. I effectively lose the mouse on the server and have to reboot.
@p12tic commented on GitHub (Jan 10, 2021):
I've reopened #775, so I'm closing this issue as a duplicate. Thanks for filling it and making sure this does not get unnoticed.