Skip to content
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

Memory leak, 100% CPU usage on Linux when disconnecting client #637

Closed
ghost opened this issue Apr 24, 2020 · 6 comments
Closed

Memory leak, 100% CPU usage on Linux when disconnecting client #637

ghost opened this issue Apr 24, 2020 · 6 comments

Comments

@ghost
Copy link

ghost commented Apr 24, 2020

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 100% CPU use on MacOS 10.13.6 #629
  • Does this bug prevent you from using Barrier entirely? No
@modelmat
Copy link

Building from git fixed this for me; the latest release is from last year and I believe #557 in February fixed this issue.

@nikolas-digitalBabylon
Copy link

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

@AfricaSaga
Copy link

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

@brgavino
Copy link

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.

@github-actions
Copy link

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.

@p12tic
Copy link
Member

p12tic commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants