mirror of
https://github.com/rustdesk/rustdesk.git
synced 2026-03-02 19:26:56 -05:00
RustDesk constantly maxes out one thread (CPU usage) #74
Labels
No labels
bug
documentation
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
question
unreproducible
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/rustdesk-rustdesk#74
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 @paperbenni on GitHub (Jun 20, 2021).
Whenever the rustdesk systemd service is running one CPU thread is constantly at 100%. This happens regardless of whether the device is connecting to anyone, anyone is connected to the device or even if the GUI is open or not. Stopping the systemd service immediately makes the cpu return to normal
I tested this on two machines, both are running Arch and a ryzen cpu. One has vega inbuilt graphics, one a gtx 1060
@rustdesk commented on GitHub (Jun 20, 2021):
Yes, we noticed this bug, I uploaded new build, please use the new build.
@paperbenni commented on GitHub (Jun 20, 2021):
where did you upload the build? The bug occurs with the newest github release (1.1.6)
@rustdesk commented on GitHub (Jun 20, 2021):
When did you download it?
@rustdesk commented on GitHub (Jun 20, 2021):
I did not create new release, just uploaded and overwrote.
@paperbenni commented on GitHub (Jun 25, 2021):
The fix works :)
@paperbenni commented on GitHub (Jun 27, 2021):
@rustdesk By the way I know it doesn't look pretty to create a new release with nothing in it but replacing releases causes lots of problems. For instance I think you just broke the AUR package for rustdesk. It doesn't check the validity test because it downloads from the github release URL but then checks for the old hash.
@rustdesk commented on GitHub (Jun 27, 2021):
Then how can I help you?