mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #715] Barrier server uses 100% CPU and all available memory #563
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#563
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Souravgoswami on GitHub (May 30, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/715
Operating Systems
Both computers are running Arch Linux x86_64.
Server
Arch Linux x86_64
Client
Arch Linux x86_64
Issue
When switching to the client, barrier started using all the available memory (RAM + ZRAM) on the server and 100% of a CPU core. Which caused frozen system. This happens after each reboot.
Barrier Version
2.3.2
Steps to reproduce bug
Other info
Screenshots
Gnome System Monitor
Htop
@shymega commented on GitHub (May 30, 2020):
Yeah, we have a fair few bug reports with regards to Barrier's memory leaks. I'll mark this is critical and as a bug for the moment, and we'll try to make a fix soon.
@Studio5086 commented on GitHub (Jun 30, 2020):
Same here on two Windows 10 Pro 1909 machines. Had do uninstall it to make my Laptop useable again.
@raid1 commented on GitHub (Aug 6, 2020):
Same here with barriers running on Ubuntu 20.04.1 LTS
I just killed my whole X session and lost lots of open/unsaved work because the memory consumption of barrier rendered my machine unusable. Please try to fix fast! Let me know if you need more details which can help you.
@p12tic commented on GitHub (Aug 6, 2020):
@raid1: Does Barrier 2.3.3 fix this issue for you?
@raid1 commented on GitHub (Aug 6, 2020):
Sorry, I forgot to mention that I've tried with 2.3.3 (latest)
@Souravgoswami commented on GitHub (Aug 11, 2020):
On Arch... So far the problem is gone...
@p12tic commented on GitHub (Jan 10, 2021):
This issue has been fixed in Barrier 2.3.3.
@raid1 commented on GitHub (Jan 11, 2021):
No, as mentioned above, it's not fixed in 2.3.3
It killed my whole X session
@p12tic commented on GitHub (Jan 11, 2021):
Thanks for clarifying, I'm reopening the bug.
@lilws commented on GitHub (Feb 26, 2021):
I'm on latest version and have the same problems. It took a lot of CPU and use a lot of RAM. Normally it uses like below 20MB, several days without restart computer, it takes like 800MB and that the point problems happen. Can't migrate to another screen, log warning of connect and disconnect clients.
@krpors commented on GitHub (Apr 13, 2021):
This has been killing my laptop for quite a while now. It doesn't happen all the time, mostly randomly, say 1 time a week. Today however, I was forced to do a hard reset twice. Any developers have any tips on how I could monitor a process (Linux 'guest'), and to determine where in the code this could happen?
@rdxmb commented on GitHub (Dec 13, 2023):
Same here with
KDE neon 5.27 \n \l, which is based on ubuntu 22.04When killing barrier and restarting again, the cpu is on about ~1.7% . I will watch that.
@rdxmb commented on GitHub (Dec 13, 2023):
is this repository deprecated? For there is a duplicated issue in the other project?