-
Notifications
You must be signed in to change notification settings - Fork 67
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
ISSUE: Persistent keepalive 1, slow, unresponsive ui with high cpu and memory usage #164
Comments
Can you try setting the value to somewhere between 10-25? 1 is excessive as all persistent keep alive does is keep the VPN routing from dropping. Even wireguards official client doesn't recommend such a low number. I normally keep mine around 20-25 (servers behind a VPN and not had any issues with connectivity) |
Changing the value from 1 to 10 or 25 won't make much of a difference since the issue is the number of logs generated by the persistent keepalive and all of them are displayed on the same page without pagination/rotation. |
I think the problem is not that the keepalive value is low, it's that the "Connection Log" panel doesn't clear messages and all the keepalive/handshake messages pile up over time wasting quite a bit of memory. This is true even when the app is minimized to the tray and not even displayed on screen. |
I have to refer to this: #148 The problem is caused by the way edge handles logs. This is strictly a logging issue due to whatever issues edge has. Clearly Edge is not that good at handling logging. |
This should now be resolved in version 1.0.7 where I have implemented a log limit that can be adjusted in settings. |
Describe the issue
If persistent keepalive set to 1 ui becomes unresponsive after some time.
To Reproduce
Steps to reproduce the behavior:
Tested on official WireGuard client
Yes, never had that issue.
Screenshots and GIF's
Tunnel Config
Logs
https://gist.github.com/kot0/66e8c7db88b7144fb6186896e564fcfe
The text was updated successfully, but these errors were encountered: