-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High memory usage over time. - memory leak #395
Comments
Memory usage over 3.5GB on the server after less than a day of use. client and server v2.2.0 (built from sources) on Ubuntu 18.04 |
@shymega there are few memory leak issues reported and resolved https://github.com/symless/synergy-core/issues?utf8=%E2%9C%93&q=is%3Aissue+memory |
symless#6460 is already addressed in Barrier. |
symless#6495 has been addressed in #409. |
I'll build a "pre-release" via CI/CD when I get home for testing. |
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. |
Thanks! Less leakage is better than nothing. |
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 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. |
Hi, On debian with a VM Windows, barrier freeze completely my computer after somes minutes: The kernel kill automatically the process of barrier:
The result is the same after have disabled TSL, i use the version 2.3.2+dfsg-1+b1. |
Try with latest git please |
This issue is also happening on Ubuntu 20.04. |
Closing this issue as it's very likely to be fixed in Barrier 2.3.3 (PR #557). |
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
Other info
maybe related to issue #147
The text was updated successfully, but these errors were encountered: