github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 22:01:23 -06:00

[GH-ISSUE #837] Barrier will use lot of I/O and CPU resource when I shutdown client machine #665

New issue

Open

opened 2026-05-05 06:52:15 -06:00 by gitea-mirror · 7 comments

gitea-mirror commented

2026-05-05 06:52:15 -06:00

Owner

Originally created by @stardiviner on GitHub (Aug 16, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/837

Operating Systems

Server: Manjaro Linux (using 5.6.4 kernel)

Client: Windows 10, 1905

Barrier Version

2.3.2

Steps to reproduce bug

Barrier connection is fine. This is great, thanks for this project!!

When I shutdown the Win10 machine, the barrier server (Manjaro machine) start to use lot of I/O resource and CPU.

Other info

When did the problem start to occur? When I...
Is there a way to work around it? No
Does this bug prevent you from using Barrier entirely? No

Originally created by @stardiviner on GitHub (Aug 16, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/837 ### Operating Systems ### Server: Manjaro Linux (using 5.6.4 kernel) Client: Windows 10, 1905 ### Barrier Version ### 2.3.2 ### Steps to reproduce bug ### Barrier connection is fine. This is great, thanks for this project!! When I shutdown the Win10 machine, the barrier server (Manjaro machine) start to use lot of I/O resource and CPU. ### Other info ### * When did the problem start to occur? When I... * Is there a way to work around it? No * Does this bug prevent you from using Barrier entirely? No

gitea-mirror added the

bug

label 2026-05-05 06:52:15 -06:00

gitea-mirror commented

2026-05-05 06:52:18 -06:00

Author

Owner

@arafatzahan commented on GitHub (Aug 25, 2020):

Could not reproduce with Manjaro Host and MacOS guest all latest version

@arafatzahan commented on GitHub (Aug 25, 2020): Could not reproduce with Manjaro Host and MacOS guest all latest version

gitea-mirror commented

2026-05-05 06:52:20 -06:00

Author

Owner

@stardiviner commented on GitHub (Aug 26, 2020):

Thanks for testing and reply, 👍

Is there a way for me to debug deeper so that I can provide more information?

@stardiviner commented on GitHub (Aug 26, 2020): Thanks for testing and reply, :+1: Is there a way for me to debug deeper so that I can provide more information?

gitea-mirror commented

2026-05-05 06:52:22 -06:00

Author

Owner

@Kaik commented on GitHub (Aug 26, 2020):

I'm experiencing the same problem I had to stop using it.
Both server and client works on Fedora 31
It is hard to say what is wrong as it happened both on client and server (not at the same time). It looked like a lot of instances of barrier was spawned and one of them took 100%
There was no particular reason it seemed to occur at random.
Don't know if this might be important but I have 3 screens connected to each machine.
I remember it worked good at the beginning of the year like march/april or something hard to say now.
Installed via flathub

@Kaik commented on GitHub (Aug 26, 2020): I'm experiencing the same problem I had to stop using it. Both server and client works on Fedora 31 It is hard to say what is wrong as it happened both on client and server (not at the same time). It looked like a lot of instances of barrier was spawned and one of them took 100% There was no particular reason it seemed to occur at random. Don't know if this might be important but I have 3 screens connected to each machine. I remember it worked good at the beginning of the year like march/april or something hard to say now. Installed via flathub

gitea-mirror commented

2026-05-05 06:52:24 -06:00

Author

Owner

@stardiviner commented on GitHub (Nov 7, 2020):

I have not seen this situation for a long time. Maybe problem gone? Should I close this issue or keep it open?

@stardiviner commented on GitHub (Nov 7, 2020): I have not seen this situation for a long time. Maybe problem gone? Should I close this issue or keep it open?

gitea-mirror commented

2026-05-05 06:52:27 -06:00

Author

Owner

@weltreisender commented on GitHub (Feb 25, 2021):

Same problem for me: When my client enters VPN (and therefore cuts connection to my local network), the server CPU load rises as much, that I can't even use mouse or keyboard any more. Mostly it occurs when the mouse is on the client and then the connection gets lost. However, this does not occur always, so I cannot reproduce it exactly.

Server is Linux Mint 19.3, client is Windows 7.
Only the server CPU is affected.

@weltreisender commented on GitHub (Feb 25, 2021): Same problem for me: When my client enters VPN (and therefore cuts connection to my local network), the server CPU load rises as much, that I can't even use mouse or keyboard any more. Mostly it occurs when the mouse is on the client and then the connection gets lost. However, this does not occur always, so I cannot reproduce it exactly. Server is Linux Mint 19.3, client is Windows 7. Only the server CPU is affected.

gitea-mirror commented

2026-05-05 06:52:29 -06:00

Author

Owner

@p12tic commented on GitHub (Jun 25, 2021):

@weltreisender Thanks a lot for explanation of what you're seeing. This is enough information to start looking into this bug.

@p12tic commented on GitHub (Jun 25, 2021): @weltreisender Thanks a lot for explanation of what you're seeing. This is enough information to start looking into this bug.

gitea-mirror commented

2026-05-05 06:52:30 -06:00

Author

Owner

@victortrac commented on GitHub (Nov 17, 2022):

This happens after a few days for me. I have to kill barrier on my linux server.

@victortrac commented on GitHub (Nov 17, 2022): This happens after a few days for me. I have to kill barrier on my linux server.

No labels

Rows
Columns