mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1936] Barrier server sometimes gets stuck at 100% cpu, strace shows write(4, "\1\0\0\0\0\0\0\0", 8) #1412
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#1412
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 @victortrac on GitHub (May 7, 2023).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1936
What happened?
I run barrier server from linux and a client on MacOS. Everything works great, but every day or two, the barrier process on my linux machine shows 100% CPU usage (as seen via top) and does not work as expected - my mouse does not leave my linux server's screen edge to the macos desktop. strace shows this, with the write syscall repeating the same 4-5 lines every few minutes:
lsof shows file descriptor 4 like this:
Version
v2.4.0
Git commit hash (if applicable)
No response
If applicable, where did you install Barrier from?
archlinux community repo:
What OSes are you seeing the problem on? (Check all that apply)
Linux
What OS versions are you using?
Relevant log output
@m10d commented on GitHub (May 11, 2023):
Is the macOS machine a laptop? Are you taking, rebooting, or otherwise removing it from the server's network?
I often (always?) get a pegged CPU and non-functional mouse sharing (mouse 'stuck' on main dev box) when the client machine is taken off the network. In my case, server is ubuntu20.04, client is win10. For example, I just rebooted the windows client - and noticed barrier pegging one core. When the windows box comes back online,
barrierfunctionality is not restored.running
systemctl --user restart barrier-kvm.serviceon the server (no action on the client other than barrier client auto-runs on boot) does restore mouse-sharing functionality.In my case as best I can tell, this spinning bug has only been exercised by taking the machine off the network. I came to submit a bug - but it's not looking like this wonderful project is not actively maintained :(
In my
strace, I see an infinite loop around reading from a socket (which sounds plausible given my reproduction, possibly not for yours)@victortrac commented on GitHub (May 15, 2023):
@m10d Yup, the macOS machine is a mostly stationary laptop. I suppose the network could blip, but it's not being actively taken off the network for this issue to happen.
Based on your strace, I think you are experiencing a different problem.
@ylluminate commented on GitHub (May 31, 2023):
AFAIK, the project has moved to: https://github.com/input-leap/input-leap
@m10d commented on GitHub (Sep 30, 2023):
Note for future readers: hopefully soon ^ but input-leap is not quite ready yet.
I was able to build linux trivially; but after installing and running it on my main/dev box I found:
Crossing fingers for their 3.0 release!