mirror of
https://github.com/1Remote/1Remote.git
synced 2026-04-25 13:36:03 +03:00
[GH-ISSUE #192] PRemoteM hogs CPU when opening many SSH connections #165
Labels
No labels
area-configuration
area-ct-app
area-ct-rdp
area-ct-remoteapp
area-ct-ssh
area-ct-vnc
area-launcher
area-list
area-tags
area-teamwork
bug
chore
dependencies
general-build/ci
general-performance
general-refactor
general-security
general-supportive
general-ux
meta-documentation
meta-enhancement
meta-enhancement
meta-feature
meta-help-wanted
meta-unknown-error
priority-hi
priority-low
pull-request
question
resolution-duplicate
resolution-invalid
resolution-wontfix
stale
task-put-off
task-still-considering
task-working-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/1Remote#165
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 @BrommD on GitHub (Jan 25, 2022).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/192
Originally assigned to: @VShawn on GitHub.
Describe the bug
When opening some remote connections, the PRemoteM main executable starts consuming CPU to the max.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
main EXE not using any CPU when not being used
Screenshots

Desktop (please complete the following information):

Additional context
maybe with WIn10 Upgrade 21H1, I did this last week... before of that, there was no high CPU usage
@BrommD commented on GitHub (Jan 25, 2022):
BTW as long it hogs all CPU, I switch it to "low priority" and "CPU affinity" to one core after startup, so it runs acceptable
@majkinetor commented on GitHub (Jan 25, 2022):
Can't confirm this with 2 SSH + 2 RDP connections. CPU never goes over 3% on my machine.
@BrommD commented on GitHub (Jan 25, 2022):
well, did an OS reboot and got now

which is not 90%, but still wondering, why ~15% CPU is required for the subprocesses.... any polling functions
@majkinetor commented on GitHub (Jan 25, 2022):
Yeah, that is high. I wonder if that is specific to your system. Have you tried some other machine?
@majkinetor commented on GitHub (Jan 25, 2022):
BTW, I don't have latest windows update, I intentionally disable that because fuck ups rule rather then exception.
@BrommD commented on GitHub (Jan 25, 2022):
look at screenshot :) you don't get "enterprise" as a regular user. And yes, I need them open, sometimes more.... Logs are looking quite unspectacular, only one, which might be an issue is:
@BrommD commented on GitHub (Jan 25, 2022):
@majkinetor commented on GitHub (Jan 25, 2022):
You didn't answer anything but 1 question @BrommD
@BrommD commented on GitHub (Jan 25, 2022):
ok,
Do you have something funky in logs?
see above
Does it require that many connections or it happens with few of them?
yes it does (also answered above)
Do you have AV software on and if so does it change anything when you disable it?
MS Defender, cannot change settings, maintained by AD admins. maybe an issue.. But I've moved the complete PremoteM folder within an excluded folder (excluded from AV scan/checks). It does not change CPU usage, which is still 15-25% now using ~10 open SSH connections...
thx
Dejan
@majkinetor commented on GitHub (Jan 25, 2022):
I can confirm this. I reproduced it like this:
test3here)This doesn't happen with RDP. The CPU goes linearly. My laptop cooler started working ASAP.
@VShawn commented on GitHub (Jan 26, 2022):
then the problem may be with the integrated external exe. the ssh session periodically checks to see if its own Kitty process has the focus. It may be that when the number of ssh is large, this periodic check brings performance problems. I've never had more than 5 ssh open so never noticed this.
The above is not confirmed, performance debugging is required.
@VShawn commented on GitHub (Jan 26, 2022):
I think I have fix it. You can try this pre-release.
PRemoteM 0.6.2 alpha.zip
@BrommD commented on GitHub (Jan 26, 2022):
looks good, 18 ssh sessions open and this


but it was a little complicated to start them up with this verison, as it seems that all SSH sessions settings were recognized as new ("host fingerprint changed" and "move settings to registry" windows), issues was, the pop-up to request either "accept new host" and "move settings to registry)
is shown and pops away again quickly, so one cannot approve question. I had to reconnect up to 10 times each session to have this box being there long enough to get it done....
:)
thx, Dejan
@VShawn commented on GitHub (Jan 26, 2022):
Oh, this is beacuse I change the default location of KiTTY in 0.6.2 for #183 (moved to
./KittyfromAppData/PRemoteM/Kitty), so the old cached can not be read by the new KiTTY, you have to check the pop-up again.BTW, you have to handle the pop-up again if you delete the folder
./Kitty.