github-starred/barrier

Fork 0

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

[GH-ISSUE #395] High memory usage over time. - memory leak #312

New issue

Closed

opened 2026-05-05 06:00:25 -06:00 by gitea-mirror · 16 comments

gitea-mirror commented

2026-05-05 06:00:25 -06:00

Owner

Originally created by @Benchwork on GitHub (Aug 12, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/395

Operating Systems

Server: windows 10 pro, v1809 build 17763.652

Client: windows 10 Enterprise v1809 build 17134.885

Barrier Version

Server: 2.2.0 & 2.3.1

Client: 2.2.0 & 2.3.1

Steps to reproduce bug

installed
switch from interactive configuration to file based.
reboot both systems and validate all is working,
use barrier for a few days, and watch Barriers continue to use more ram.
run out of RAM (barriers uses over 4GB of RAM) other programs crash and the resources are
Kill process in task manager, Barriers restarts itself and go to step 3.

Other info

When did the problem start to occur? Slowly over a few days.
Is there a way to work around it? Yes, you can kill and restart barrier
Does this bug prevent you from using Barrier entirely? No

maybe related to issue #147

Originally created by @Benchwork on GitHub (Aug 12, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/395 ### Operating Systems ### Server: windows 10 pro, v1809 build 17763.652 Client: windows 10 Enterprise v1809 build 17134.885 ### Barrier Version ### Server: 2.2.0 & 2.3.1 Client: 2.2.0 & 2.3.1 ### Steps to reproduce bug ### 0. installed 1. switch from interactive configuration to file based. 2. reboot both systems and validate all is working, 3. use barrier for a few days, and watch Barriers continue to use more ram. 4. run out of RAM (barriers uses over 4GB of RAM) other programs crash and the resources are 5. Kill process in task manager, Barriers restarts itself and go to step 3. ### Other info ### * When did the problem start to occur? Slowly over a few days. * Is there a way to work around it? Yes, you can kill and restart barrier * Does this bug prevent you from using Barrier entirely? No maybe related to issue #147

gitea-mirror

2026-05-05 06:00:25 -06:00

closed this issue
added the
bug

help wanted

windows

critical
labels

gitea-mirror commented

2026-05-05 06:00:31 -06:00

Author

Owner

@igordovgaluk commented on GitHub (Aug 22, 2019):

Memory usage over 3.5GB on the server after less than a day of use.
One client (laptop) connected and disconnected a few times over the period.

client and server v2.2.0 (built from sources) on Ubuntu 18.04

@igordovgaluk commented on GitHub (Aug 22, 2019): Memory usage over 3.5GB on the server after less than a day of use. One client (laptop) connected and disconnected a few times over the period. client and server v2.2.0 (built from sources) on Ubuntu 18.04

gitea-mirror commented

2026-05-05 06:00:36 -06:00

Author

Owner

@igordovgaluk commented on GitHub (Aug 22, 2019):

@shymega there are few memory leak issues reported and resolved
https://github.com/symless/synergy-core/issues/6460
https://github.com/symless/synergy-core/issues/6495

https://github.com/symless/synergy-core/issues?utf8=%E2%9C%93&q=is%3Aissue+memory

@igordovgaluk commented on GitHub (Aug 22, 2019): @shymega there are few memory leak issues reported and resolved https://github.com/symless/synergy-core/issues/6460 https://github.com/symless/synergy-core/issues/6495 https://github.com/symless/synergy-core/issues?utf8=%E2%9C%93&q=is%3Aissue+memory

gitea-mirror commented

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

Author

Owner

@p12tic commented on GitHub (Aug 22, 2019):

symless#6460 is already addressed in Barrier.

@p12tic commented on GitHub (Aug 22, 2019): symless#6460 is already addressed in Barrier.

gitea-mirror commented

2026-05-05 06:00:41 -06:00

Author

Owner

@p12tic commented on GitHub (Aug 22, 2019):

symless#6495 has been addressed in https://github.com/debauchee/barrier/pull/409.

@p12tic commented on GitHub (Aug 22, 2019): symless#6495 has been addressed in https://github.com/debauchee/barrier/pull/409.

gitea-mirror commented

2026-05-05 06:00:49 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Aug 22, 2019):

I'll build a "pre-release" via CI/CD when I get home for testing.

@AdrianKoshka commented on GitHub (Aug 22, 2019): I'll build a "pre-release" via CI/CD when I get home for testing.

gitea-mirror commented

2026-05-05 06:00:53 -06:00

Author

Owner

@p12tic commented on GitHub (Aug 22, 2019):

I saw that there were still some memory usage growth even after the recent fixes, but the magnitude was roughly 10-20 times smaller. So the bug is not completely fixed. Unfortunately full fix is a little more involved as the memory is allocated in area used by multiple threads, so it will take some time.

@p12tic commented on GitHub (Aug 22, 2019): I saw that there were still some memory usage growth even after the recent fixes, but the magnitude was roughly 10-20 times smaller. So the bug is not completely fixed. Unfortunately full fix is a little more involved as the memory is allocated in area used by multiple threads, so it will take some time.

gitea-mirror commented

2026-05-05 06:00:58 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Aug 22, 2019):

Thanks! Less leakage is better than nothing.

@AdrianKoshka commented on GitHub (Aug 22, 2019): Thanks! Less leakage is better than nothing.

gitea-mirror commented

2026-05-05 06:01:01 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Aug 22, 2019):

If anyone is willing to, it'd be appreciated to test this alpha release which includes some memory leaking alleviation. https://github.com/debauchee/barrier/releases/tag/v2.3.2-alpha

@AdrianKoshka commented on GitHub (Aug 22, 2019): If anyone is willing to, it'd be appreciated to test this alpha release which includes some memory leaking alleviation. https://github.com/debauchee/barrier/releases/tag/v2.3.2-alpha

gitea-mirror commented

2026-05-05 06:01:04 -06:00

Author

Owner

@noisyshape commented on GitHub (Aug 23, 2019):

@AdrianKoshka I've tested the master branch on Linux and Windows and both look good. SSL connections leak much less and non-SSL connections appear unchanged.

@noisyshape commented on GitHub (Aug 23, 2019): @AdrianKoshka I've tested the master branch on Linux and Windows and both look good. SSL connections leak much less and non-SSL connections appear unchanged.

gitea-mirror commented

2026-05-05 06:01:06 -06:00

Author

Owner

@cowbe0x004 commented on GitHub (Sep 18, 2019):

I'm afraid this is still happening on Windows client. I'm using 2.3.2-alpha. Both server and client use the same version, but the server is fine. This started happening after I updated to Windows 1903 OS build 18362.356.

This is about 5 mins after I started barrier.

EDIT: looks like this is due to encryption. Turned off Enable SSL and it's back to normal.

@cowbe0x004 commented on GitHub (Sep 18, 2019): I'm afraid this is still happening on Windows client. I'm using 2.3.2-alpha. Both server and client use the same version, but the server is fine. This started happening after I updated to Windows 1903 OS build 18362.356. This is about 5 mins after I started barrier. ![Untitled](https://user-images.githubusercontent.com/3072913/65100196-e7927380-d995-11e9-9f81-4b74ec4fbd33.png) EDIT: looks like this is due to encryption. Turned off Enable SSL and it's back to normal.

gitea-mirror commented

2026-05-05 06:01:09 -06:00

Author

Owner

@salcin commented on GitHub (Dec 14, 2019):

Hi,

On debian with a VM Windows, barrier freeze completely my computer after somes minutes:

The kernel kill automatically the process of barrier:

[  987.308292] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service,task=barriers,pid=5826,uid=1000
[  987.308304] Out of memory: Killed process 5826 (barriers) total-vm:6994716kB, anon-rss:6912880kB, file-rss:0kB, shmem-rss:0kB
[  987.430457] oom_reaper: reaped process 5826 (barriers), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

The result is the same after have disabled TSL, i use the version 2.3.2+dfsg-1+b1.

@salcin commented on GitHub (Dec 14, 2019): Hi, On debian with a VM Windows, barrier freeze completely my computer after somes minutes: The kernel kill automatically the process of barrier: [ 987.308292] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service,task=barriers,pid=5826,uid=1000 [ 987.308304] Out of memory: Killed process 5826 (barriers) total-vm:6994716kB, anon-rss:6912880kB, file-rss:0kB, shmem-rss:0kB [ 987.430457] oom_reaper: reaped process 5826 (barriers), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB The result is the same after have disabled TSL, i use the version 2.3.2+dfsg-1+b1.

gitea-mirror commented

2026-05-05 06:01:10 -06:00

Author

Owner

@williamoliveira commented on GitHub (Apr 23, 2020):

It got pretty wild on my machine (Ubuntu 18.04)

Happened at the server after a client disconnected

@williamoliveira commented on GitHub (Apr 23, 2020): It got pretty wild on my machine (Ubuntu 18.04) ![Screenshot from 2020-04-22 21-07-30](https://user-images.githubusercontent.com/6340344/80045328-65df6700-84dd-11ea-9b6a-d8367f8ff789.png) Happened at the server after a client disconnected

gitea-mirror commented

2026-05-05 06:01:12 -06:00

Author

Owner

@isgursoy commented on GitHub (May 16, 2020):

It got pretty wild on my machine (Ubuntu 18.04)

Happened at the server after a client disconnected

for me too

@isgursoy commented on GitHub (May 16, 2020): > It got pretty wild on my machine (Ubuntu 18.04) > ![Screenshot from 2020-04-22 21-07-30](https://user-images.githubusercontent.com/6340344/80045328-65df6700-84dd-11ea-9b6a-d8367f8ff789.png) > > Happened at the server after a client disconnected for me too

gitea-mirror commented

2026-05-05 06:01:14 -06:00

Author

Owner

@mirh commented on GitHub (May 16, 2020):

Try with latest git please
https://github.com/debauchee/barrier/pull/557

@mirh commented on GitHub (May 16, 2020): Try with latest git please https://github.com/debauchee/barrier/pull/557

gitea-mirror commented

2026-05-05 06:01:16 -06:00

Author

Owner

@knoriy commented on GitHub (Jul 9, 2020):

This issue is also happening on Ubuntu 20.04.

@knoriy commented on GitHub (Jul 9, 2020): This issue is also happening on Ubuntu 20.04.

gitea-mirror commented

2026-05-05 06:01:18 -06:00

Author

Owner

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

Closing this issue as it's very likely to be fixed in Barrier 2.3.3 (PR #557).

@p12tic commented on GitHub (Jan 10, 2021): Closing this issue as it's very likely to be fixed in Barrier 2.3.3 (PR #557).

No labels

Rows
Columns