You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this something you can debug and fix? Send a pull request! Bug fixes and documentation fixes are welcome.
I have searched on the issue tracker for a related issue.
Version
2.5.2
What OS are you seeing the problem on?
Windows
Description
I am faced with the problem of large memory leaks when using the Xray-client with tun2socks (for local socks proxy) on Windows 11, here is my Xray config:
Leaks reaches 2GB+ on Tun2socks.exe and 1GB+ on Xray.exe
I guess my virtual adapter is being created incorrectly in some way and traffic just starts to overflow the Tun2socks and Xray stacks. Maybe someone can provide me with other tools for local socks-proxying to the xray-client (at 127.0.0.1:10808) I will be very grateful!
[Tun2socks] time="2024-08-16T10:48:56+03:00" level=warning msg="[UDP] dial "server-ip": connect to 127.0.0.1:10808: dial tcp 127.0.0.1:10808: bind: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full."
[Tun2socks] time="2024-08-16T10:48:58+03:00" level=warning msg="[UDP] dial "server-ip": connect to 127.0.0.1:10808: dial tcp 127.0.0.1:10808: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
How to Reproduce
In cmd run Xray-core as admin with config from the description :
Verify steps
Version
2.5.2
What OS are you seeing the problem on?
Windows
Description
I am faced with the problem of large memory leaks when using the Xray-client with tun2socks (for local socks proxy) on Windows 11, here is my Xray config:
Xray-client config.json
Leaks reaches 2GB+ on Tun2socks.exe and 1GB+ on Xray.exe
I guess my virtual adapter is being created incorrectly in some way and traffic just starts to overflow the Tun2socks and Xray stacks. Maybe someone can provide me with other tools for local socks-proxying to the xray-client (at 127.0.0.1:10808) I will be very grateful!
CLI or Config
Logs
How to Reproduce
The text was updated successfully, but these errors were encountered: