search

TunnlTo / desktop-app

TunnlTo is a Windows WireGuard VPN client built for split tunnelling.
https://tunnl.to
1.11k stars 53 forks source link

ISSUE: Persistent keepalive 1, slow, unresponsive ui with high cpu and memory usage #164

Closed kot0 closed 1 month ago

kot0 commented 3 months ago

Describe the issue If persistent keepalive set to 1 ui becomes unresponsive after some time.

To Reproduce Steps to reproduce the behavior:

  1. Connect to vpn with persistent keepalive set to 1
  2. Wait 10 hours
  3. See that msedgewebview2.exe using 1.4G of ram and 18% of cpu or more

Tested on official WireGuard client Yes, never had that issue.

Screenshots and GIF's image image

Tunnel Config image image

Logs https://gist.github.com/kot0/66e8c7db88b7144fb6186896e564fcfe

vithusel commented 3 months ago

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)

kot0 commented 3 months ago

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.

Setsu-BHMT commented 3 months ago

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.

runner1409 commented 2 months ago

I have to refer to this: https://github.com/TunnlTo/desktop-app/issues/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.

brendanosborne commented 1 month ago

This should now be resolved in version 1.0.7 where I have implemented a log limit that can be adjusted in settings.