github-starred/barrier

Fork 0

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

[GH-ISSUE #637] Memory leak, 100% CPU usage on Linux when disconnecting client #506

New issue

Closed

opened 2026-05-05 06:33:20 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 06:33:20 -06:00

Owner

Originally created by @ghost on GitHub (Apr 24, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/637

Operating Systems

Server: Linux Manjaro

Client: Windows 10 Version 1809 (OS Build 17763, 1098)

Barrier Version

2.3.2-RELEASE-00000000

Steps to reproduce bug

Connect server (linux) and client (windows)
Shut down the client (windows)
Bug occurs. CPU usage on the server (linux) increases to about 20% and memory usage increases until 100% is used up. Then the system becomes difficult to use

Other info

The error happens consistently
process name that uses memory is "barriers"
CPU usage increases when 100% memory is used.
The error happens only when the client is actually shut down - It does not happen when it is just disconnected
Workaround is: Restart barrier server application. Quit barrier application on server, this will bring the server back to normal
the bug can be repeated without shutting down the server (linux) just by restarting barrier and reconnecting the client
this is possibly related to bug #629
Does this bug prevent you from using Barrier entirely? No

Originally created by @ghost on GitHub (Apr 24, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/637 ### Operating Systems ### Server: Linux Manjaro Client: Windows 10 Version 1809 (OS Build 17763, 1098) ### Barrier Version ### 2.3.2-RELEASE-00000000 ### Steps to reproduce bug ### 1. Connect server (linux) and client (windows) 2. Shut down the client (windows) 3. Bug occurs. CPU usage on the server (linux) increases to about 20% and memory usage increases until 100% is used up. Then the system becomes difficult to use ### Other info ### * The error happens consistently * process name that uses memory is "barriers" * CPU usage increases when 100% memory is used. * The error happens only when the client is actually shut down - It does not happen when it is just disconnected * Workaround is: Restart barrier server application. Quit barrier application on server, this will bring the server back to normal * the bug can be repeated without shutting down the server (linux) just by restarting barrier and reconnecting the client * this is possibly related to bug #629 * Does this bug prevent you from using Barrier entirely? No

gitea-mirror closed this issue

2026-05-05 06:33:22 -06:00

gitea-mirror commented

2026-05-05 06:33:24 -06:00

Author

Owner

@modelmat commented on GitHub (Apr 25, 2020):

Building from git fixed this for me; the latest release is from last year and I believe https://github.com/debauchee/barrier/pull/557 in February fixed this issue.

@modelmat commented on GitHub (Apr 25, 2020): Building from git fixed this for me; the latest release is from last year and I believe https://github.com/debauchee/barrier/pull/557 in February fixed this issue.

gitea-mirror commented

2026-05-05 06:33:27 -06:00

Author

Owner

@nikolas-digitalBabylon commented on GitHub (May 1, 2020):

I can confirm the bug with the snap package on Ubuntu 18.04LTS host and Windows 10 client.

@nikolas-digitalBabylon commented on GitHub (May 1, 2020): I can confirm the bug with the snap package on Ubuntu 18.04LTS host and Windows 10 client.

gitea-mirror commented

2026-05-05 06:33:30 -06:00

Author

Owner

@AfricaSaga commented on GitHub (Jun 18, 2020):

Same here, CentOS 8 server / Win10Pro client
Memory usage went to 6+Gigs, crippled computer
Had to restart barrier server

@AfricaSaga commented on GitHub (Jun 18, 2020): Same here, CentOS 8 server / Win10Pro client Memory usage went to 6+Gigs, crippled computer Had to restart barrier server

gitea-mirror commented

2026-05-05 06:33:32 -06:00

Author

Owner

@brgavino commented on GitHub (Jul 22, 2020):

After experiencing this issue consistently with a Win10 client and a Clear Linux Host, 2.3.3 client/server fixes this issue through multiple disconnects client/server restarts etc.

@brgavino commented on GitHub (Jul 22, 2020): After experiencing this issue consistently with a Win10 client and a Clear Linux Host, 2.3.3 client/server fixes this issue through multiple disconnects client/server restarts etc.

gitea-mirror commented

2026-05-05 06:33:35 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 23, 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 23, 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.

gitea-mirror commented

2026-05-05 06:33:37 -06:00

Author

Owner

@p12tic commented on GitHub (Jan 10, 2021):

2.3.3 fixed this issue.

Reopening and closing just that it does not look like a bot closed the issue for no reason.

@p12tic commented on GitHub (Jan 10, 2021): 2.3.3 fixed this issue. Reopening and closing just that it does not look like a bot closed the issue for no reason.

No labels

Rows
Columns