Windows 10环境下内存占用问题

[KamenRiderKuuga]

Describe the bug

版本：ktctl_0.3.7_Windows_x86_64

在Windows环境使用ktctl connect命令， 启动完毕，系统显示：

All looks good, now you can access to resources in the kubernetes cluster

此时内存占用接近2GB

开启一段时间后，内存占用持续升高：

其间只是开着工具，还未开始本地代码调试等工作

Log

启动时：

11:31AM INF Using cluster context default (default)
11:31AM INF KtConnect 0.3.7 start at 33232 (windows amd64)
11:31AM INF Fetching cluster time ...
11:31AM INF Using tun2socks mode
11:31AM INF Successful create config map kt-connect-shadow-twkeg
11:31AM INF Deploying shadow pod kt-connect-shadow-twkeg in namespace default
11:31AM INF Waiting for pod kt-connect-shadow-twkeg ...
11:32AM INF Pod kt-connect-shadow-twkeg is ready
11:32AM INF Port forward local:39036 -> pod kt-connect-shadow-twkeg:22 established
11:32AM INF Socks proxy established
2023/03/11 11:32:06 Using existing driver 0.14
2023/03/11 11:32:06 Creating adapter
11:32AM INF Tun device KtConnectTunnel is ready
11:32AM INF Adding route to 10.233.0.0/16
11:32AM INF Adding route to 192.168.100.128/25
11:32AM INF Adding route to 192.168.100.64/26
11:32AM INF Adding route to 192.168.100.32/27
11:32AM INF Adding route to 192.168.100.0/28
11:32AM INF Adding route to 192.168.100.16/29
11:32AM INF Adding route to 192.168.100.28/30
11:32AM INF Adding route to 192.168.100.24/31
11:32AM INF Adding route to 192.168.100.27/32
11:32AM INF Route to tun device completed
11:32AM INF Setting up dns in local mode
11:32AM INF Port forward local:60248 -> pod kt-connect-shadow-twkeg:53 established
11:32AM INF Setup local DNS with upstream [tcp:127.0.0.1:60248 udp:192.168.0.7:53]
11:32AM INF Creating udp dns on port 53
11:32AM INF ---------------------------------------------------------------
11:32AM INF  All looks good, now you can access to resources in the kubernetes cluster
11:32AM INF ---------------------------------------------------------------

运行时：

11:33AM WRN Failed to lookup wpad.company.com. (1) in dns (192.168.0.7:53) error="dial udp 192.168.0.7:53: connect: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full."
11:34AM WRN Failed to lookup 1.airmavi.com. (1) in dns (192.168.0.7:53) error="dial udp 192.168.0.7:53: connect: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full."
11:35AM WRN Failed to lookup ns.dns.in-addr.arpa. (1) in dns (127.0.0.1:60248) error="dial tcp 127.0.0.1:60248: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
11:35AM WRN Failed to lookup company.com. (2) in dns (127.0.0.1:60248) error="dial tcp 127.0.0.1:60248: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
11:35AM WRN Failed to lookup _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.company.com. (33) in dns (127.0.0.1:60248) error="dial tcp 127.0.0.1:60248: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
11:35AM WRN Failed to lookup _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.company.com. (33) in dns (127.0.0.1:60248) error="dial tcp 127.0.0.1:60248: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
11:35AM WRN Failed to lookup dc2.company.com. (1) in dns (127.0.0.1:60248) error="dial tcp 127.0.0.1:60248: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
11:35AM WRN Failed to lookup dc2.company.com. (1) in dns (127.0.0.1:60248) error="dial tcp 127.0.0.1:60248: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
11:38AM WRN Failed to lookup 27.100.168.192.in-addr.arpa. (2) in dns (192.168.0.7:53) error="dial udp 192.168.0.7:53: connect: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full."
11:39AM WRN Failed to lookup 28.100.168.192.in-addr.arpa. (2) in dns (192.168.0.7:53) error="dial udp 192.168.0.7:53: connect: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full."
11:39AM WRN Failed to lookup 32.100.168.192.in-addr.arpa. (2) in dns (192.168.0.7:53) error="dial udp 192.168.0.7:53: connect: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full."
11:40AM WRN Failed to lookup 64.100.168.192.in-addr.arpa. (2) in dns (192.168.0.7:53) error="dial udp 192.168.0.7:53: connect: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full."
11:41AM WRN Failed to lookup 128.100.168.192.in-addr.arpa. (2) in dns (192.168.0.7:53) error="dial udp 192.168.0.7:53: connect: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full."
11:41AM WRN Failed to lookup kamenriderkuuga.company.com. (6) in dns (192.168.0.7:53) error="dial udp 192.168.0.7:53: connect: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full."

Additional context

Question1: 工具的正常内存占用情况就是这样吗？ Question2: 是否可能和公司的网络环境有关？

#291