mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #629] 100% CPU use on MacOS 10.13.6 #497
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#497
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 @ghost on GitHub (Apr 17, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/629
Sadly there's not much info I can offer here - Barrier uses 100% CPU after about 5 minutes of running, even with no other servers on the network, and continues to do so until it is closed.
@IPWright83 commented on GitHub (Apr 22, 2020):
I've been using barrier for a couple of weeks, it was running pretty much stably but I'm now noticing huge CPU usage in Windows 10 x64 too.
v2.3.2-snapshot-210c2b70
@simons-public commented on GitHub (May 3, 2020):
Which version are you using? I've got a build posted from the #648 pull request that changes how the app bundle is packaged and uses recent versions of Qt and OpenSSL if you want to try it.
@galkinvv commented on GitHub (May 6, 2020):
And about cpu usage on windows - there is 2 PRs since that release that should improve the situation:
#557 (Merged)
#656 (Just created, not well-tested yet)
The windows binaries with both fixes are currently available in #656 artifacts at https://dev.azure.com/debauchee/Barrier/_build/results?buildId=167&view=artifacts&type=publishedArtifacts
@github-actions[bot] commented on GitHub (Sep 24, 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.
@p12tic commented on GitHub (Jan 10, 2021):
This bug should be fixed as of 2.3.3. Please reopen if that's not the case.