github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #552] Windows 10 (client) and windows 7 (server) sometimes barrier jumps to 4gb memory use and then mouse and keyboard stops working (for most part) #432

New issue

Open

opened 2026-05-05 06:22:32 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 06:22:32 -06:00

Owner

Originally created by @reenenlaurie on GitHub (Feb 5, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/552

Operating Systems

Server: Windows 7 version 6.1 Build 7601: service pack 1)

Client: Windows 10 version 1809 (OS build 17763.805)

Barrier Version

2.3.2-snapshot-210cb70 (both)

Steps to reproduce bug

Bug is intermittent, I will try to find steps to reproduce.
Always happens on server side when the cursor would move to the clientside PC
Ctrl-Alt-Delete still works (serverside)
I can then open task manager, and see barrier using 4gb of memory

It might be related to the other software I use that changes the mouse cursor roughly when I am exiting the server? I couldn't reproduce, but while trying to I did get that barrier wasn't moving the mouse over to the client for a second or two. The software is submitting fairly big amounts of data to the network so could in theory be clogging the whole network pipe? I don't think this would be the issue, but who knows...

Other info

Is there a way to work around it? Yes

I can exit barrier by telling windows I want to log on as a different user, then selecting myself again from that window, then I don't know why or how, but windows kills barrier when this is selected.

When did the problem start to occur? When I...
It's happened about 4 times over about 3 weeks of use
Does this bug prevent you from using Barrier entirely? Yes/No
It is highly unfun, but No I can and do continue to use barrier.
I'll take a photo if it happens again, and take more careful notes of what I was busy with. (screenshots will probably not work)

Originally created by @reenenlaurie on GitHub (Feb 5, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/552 ### Operating Systems ### Server: Windows 7 version 6.1 Build 7601: service pack 1) Client: Windows 10 version 1809 (OS build 17763.805) ### Barrier Version ### 2.3.2-snapshot-210cb70 (both) ### Steps to reproduce bug ### 1. Bug is intermittent, I will try to find steps to reproduce. 2. Always happens on server side when the cursor would move to the clientside PC 3. Ctrl-Alt-Delete still works (serverside) 4. I can then open task manager, and see barrier using 4gb of memory It might be related to the other software I use that changes the mouse cursor roughly when I am exiting the server? I couldn't reproduce, but while trying to I did get that barrier wasn't moving the mouse over to the client for a second or two. The software is submitting fairly big amounts of data to the network so could in theory be clogging the whole network pipe? I don't think this would be the issue, but who knows... ### Other info ### * Is there a way to work around it? Yes I can exit barrier by telling windows I want to log on as a different user, then selecting myself again from that window, then I don't know why or how, but windows kills barrier when this is selected. * When did the problem start to occur? When I... It's happened about 4 times over about 3 weeks of use * Does this bug prevent you from using Barrier entirely? Yes/No It is highly unfun, but No I can and do continue to use barrier. * I'll take a photo if it happens again, and take more careful notes of what I was busy with. (screenshots will probably not work)

gitea-mirror added the

bug

windows

labels 2026-05-05 06:22:32 -06:00

gitea-mirror commented

2026-05-05 06:22:38 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 30, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 30, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

No labels

Rows
Columns