Skip to content
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

high CPU load with VPN service mode #1436

Open
2 tasks done
LazyBramble opened this issue Oct 24, 2024 · 1 comment
Open
2 tasks done

high CPU load with VPN service mode #1436

LazyBramble opened this issue Oct 24, 2024 · 1 comment
Labels
bug Something isn't working reviewed

Comments

@LazyBramble
Copy link

Search first

  • I searched and no similar issues were found

What Happened?

After a short time, after connecting in VPN Service mode, the CPU usage starts to grow to 100%. Restarting helps for 5-10 minutes, but then it grows again to 100%.

Minimal Reproducible Example (MRE)

Vpn Service mode
TUN gvisor
TLS fragment off
WARP off

Expected Behavior

No response

Version

2.5.7

Platform/OS

Windows

Additional Context

No response

Application Config Options

No response

Relevant log output

No response

Are you willing to submit a PR? If you know how to fix the bug.

  • I'm willing to submit a PR (Thank you!)
@LazyBramble LazyBramble added the bug Something isn't working label Oct 24, 2024
@Amirali-Amirifar
Copy link
Contributor

Amirali-Amirifar commented Nov 12, 2024

I can confirm this.
It seems to have memory leaks, which may also affect CPU usage.
Screenshot 2024-11-12 at 11 08 16 PM
I suspect it is related to libcore.
In my case, it occurred while using the system proxy mode.
Until 2-3 hours, the load was negligible, but after that, I had a recorder consuming 33GB of memory and using 122% of the CPU!

Edit:
After further inspection. It appears most of the leaks are coming from Status logs memory allocation

      1 (112 bytes) ROOT LEAK: 0x600000e3c540 [112]  length: 109  "{"connections-in":9,"connections-out":42,"downlink":0,"downlink-total":29043,"upli..."
      1 (112 bytes) ROOT LEAK: 0x600000e64690 [112]  length: 109  "{"connections-in":9,"connections-out":36,"downlink":0,"downlink-total":29043,"upli..."
      1 (112 bytes) ROOT LEAK: 0x600000e64cb0 [112]  length: 110  "{"connections-in":10,"connections-out":45,"downlink":0,"downlink-total":29043,"upl..."
      1 (112 bytes) ROOT LEAK: 0x600000e64ee0 [112]  length: 111  "{"connections-in":3,"connections-out":22,"downlink":1736,"downlink-total":10372,"u..."
      1 (112 bytes) ROOT LEAK: 0x600000e65730 [112]  length: 111  "{"connections-in":10,"connections-out":197,"downlink":0,"downlink-total":49303,"up..."
      1 (112 bytes) ROOT LEAK: 0x600000e658f0 [112]  length: 111  "{"connections-in":10,"connections-out":122,"downlink":0,"downlink-total":48582,"up..."
      1 (112 bytes) ROOT LEAK: 0x600000e65b20 [112]  length: 111  "{"connections-in":10,"connections-out":143,"downlink":0,"downlink-total":48960,"up..."
      1 (112 bytes) ROOT LEAK: 0x600000e66b50 [112]  length: 109  "{"connections-in":9,"connections-out":59,"downlink":0,"downlink-total":35200,"upli..."
      1 (112 bytes) ROOT LEAK: 0x600000e66bc0 [112]  length: 111  "{"connections-in":10,"connections-out":141,"downlink":0,"downlink-total":48960,"up..."
      1 (112 bytes) ROOT LEAK: 0x600000e67100 [112]  length: 111  "{"connections-in":10,"connections-out":146,"downlink":0,"downlink-total":48960,"up..."
      1 (112 bytes) ROOT LEAK: 0x600000e6f330 [112]  length: 111  "{"connections-in":1,"connections-out":19,"downlink":4354,"downlink-total":4612,"up..."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working reviewed
Projects
Status: No status
Development

No branches or pull requests

3 participants