[GH-ISSUE #1891] Mouse lags on M1 Mac Target for 30-60 seconds after reconnecting #1381

Open
opened 2026-05-05 07:47:09 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @Mr-Technician on GitHub (Jan 31, 2023).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1891

What happened?

I am running Barrier in server mode from my Windows Desktop and my M1 MacBook Pro is the client. After reconnecting to Barrier when my Mac is asleep, the mouse pointer freezes every few seconds. Typing also freezes. After 30 seconds to a minute, the issue seems to go away and I can move the mouse and type as if I were using the physical keyboard.

I am speculating that this could have to do with the Rosetta 2 emulation layer. The CPU usage also seems high on the client at around 10%. I don't have an ethernet adapter to test with but I doubt my WiFi is the issue.

If I disconnect manually and then reconnect, the issue does not occur.

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

No response

What OSes are you seeing the problem on? (Check all that apply)

macOS

What OS versions are you using?

macOS Ventura 13.1.

Relevant log output

No response

Any other information

No response

Originally created by @Mr-Technician on GitHub (Jan 31, 2023). Original GitHub issue: https://github.com/debauchee/barrier/issues/1891 ### What happened? I am running Barrier in server mode from my Windows Desktop and my M1 MacBook Pro is the client. After reconnecting to Barrier when my Mac is asleep, the mouse pointer freezes every few seconds. Typing also freezes. After 30 seconds to a minute, the issue seems to go away and I can move the mouse and type as if I were using the physical keyboard. I am speculating that this could have to do with the Rosetta 2 emulation layer. The CPU usage also seems high on the client at around 10%. I don't have an ethernet adapter to test with but I doubt my WiFi is the issue. If I disconnect manually and then reconnect, the issue does not occur. ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? _No response_ ### What OSes are you seeing the problem on? (Check all that apply) macOS ### What OS versions are you using? macOS Ventura 13.1. ### Relevant log output _No response_ ### Any other information _No response_
Author
Owner

@VladKorzun commented on GitHub (Feb 2, 2023):

I experience the same behavior using Barrier 2.4.0, Intel mac as a server and M1 mac as a client, both running on Monterey 12.6

<!-- gh-comment-id:1414358879 --> @VladKorzun commented on GitHub (Feb 2, 2023): I experience the same behavior using Barrier 2.4.0, Intel mac as a server and M1 mac as a client, both running on Monterey 12.6
Author
Owner

@Mr-Technician commented on GitHub (Feb 2, 2023):

I experience the same behavior using Barrier 2.4.0, Intel mac as a server and M1 mac as a client, both running on Monterey 12.6

I helped someone else setup their M1 Mac as the server and Windows desktop as the client and the issue didn't occur, so it may be limited to M1 Macs as the client.

<!-- gh-comment-id:1414384572 --> @Mr-Technician commented on GitHub (Feb 2, 2023): > I experience the same behavior using Barrier 2.4.0, Intel mac as a server and M1 mac as a client, both running on Monterey 12.6 I helped someone else setup their M1 Mac as the server and Windows desktop as the client and the issue didn't occur, so it may be limited to M1 Macs as the client.
Author
Owner

@teguhsatria892 commented on GitHub (Feb 20, 2023):

I'm using M1 too as a client, and windows as a server, maybe just uncheck 'Check clients every' option, and don't use SSL,

<!-- gh-comment-id:1436216272 --> @teguhsatria892 commented on GitHub (Feb 20, 2023): I'm using M1 too as a client, and windows as a server, maybe just uncheck 'Check clients every' option, and don't use SSL,
Author
Owner

@Mr-Technician commented on GitHub (Feb 20, 2023):

I highly doubt it is due to the SSL settings. Check clients is already disabled.

<!-- gh-comment-id:1436265671 --> @Mr-Technician commented on GitHub (Feb 20, 2023): I highly doubt it is due to the SSL settings. Check clients is already disabled.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#1381
No description provided.