-
Notifications
You must be signed in to change notification settings - Fork 471
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
udp流量转发貌似有问题,微信视频时cpu300%占用 #4
Comments
有些 UDP 流量是拿不到进程名字的,就会分配一个叫 但如果是 clash 所发的 udp,不应该拿不到的,我表示很怀疑。 |
我不确定是不是clash的问题 这是新日志 开的debug模式 |
你看看 clash 的日志吧,你给的日志也看不出这个 |
好的 我先关了 |
大佬 这是同一时间段的mellow日志和clash日志 你看能不能发现什么问题。还有就是为啥clash cpu占用没有爆炸,mellow却爆炸了 终端出现很多lsof进程 mellow日志[2019-08-15 23:13:09.753] [info] 2019/08/15 23:13:09 [Info] [2854914881] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:180.96.87.24:8080]
2019/08/15 23:13:09 [Info] [2854914881] v2ray.com/core/proxy/freedom: opening connection to udp:180.96.87.24:8080
2019/08/15 23:13:09 [Info] [491528946] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:180.96.87.24:8080]
2019/08/15 23:13:09 [Info] [491528946] v2ray.com/core/proxy/freedom: opening connection to udp:180.96.87.24:8080
[2019-08-15 23:13:09.763] [info] 2019/08/15 23:13:09 [] [udp] [unknown process] udp:180.96.87.24:8080
2019/08/15 23:13:09 [] [udp] [unknown process] udp:180.96.87.24:8080
[2019-08-15 23:13:09.764] [info] 2019/08/15 23:13:09 [Info] [684520611] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:180.96.87.24:8080]
2019/08/15 23:13:09 [Info] [1215899089] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:180.96.87.24:8080]
2019/08/15 23:13:09 [Info] [684520611] v2ray.com/core/proxy/freedom: opening connection to udp:180.96.87.24:8080
2019/08/15 23:13:09 [Info] [1215899089] v2ray.com/core/proxy/freedom: opening connection to udp:180.96.87.24:8080
[2019-08-15 23:13:09.809] [info] 2019/08/15 23:13:09 [] [udp] [unknown process] udp:123.151.144.43:8000
[2019-08-15 23:13:09.810] [info] 2019/08/15 23:13:09 [Info] [913312708] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:123.151.144.43:8000]
2019/08/15 23:13:09 [Info] [913312708] v2ray.com/core/proxy/freedom: opening connection to udp:123.151.144.43:8000
[2019-08-15 23:13:09.828] [info] 2019/08/15 23:13:09 [] [udp] [unknown process] udp:123.151.144.43:8000
[2019-08-15 23:13:09.830] [info] 2019/08/15 23:13:09 [Info] [3442036587] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:123.151.144.43:8000]
2019/08/15 23:13:09 [Info] [3442036587] v2ray.com/core/proxy/freedom: opening connection to udp:123.151.144.43:8000
[2019-08-15 23:13:09.864] [info] 2019/08/15 23:13:09 [] [udp] [unknown process] udp:180.96.87.24:8080
[2019-08-15 23:13:09.867] [info] 2019/08/15 23:13:09 [Info] [1696073386] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:180.96.87.24:8080]
[2019-08-15 23:13:09.867] [info] 2019/08/15 23:13:09 [Info] [1696073386] v2ray.com/core/proxy/freedom: opening connection to udp:180.96.87.24:8080
[2019-08-15 23:13:09.913] [info] 2019/08/15 23:13:09 [] [udp] [unknown process] udp:123.151.144.43:8000
[2019-08-15 23:13:09.916] [info] 2019/08/15 23:13:09 [] [udp] [unknown process] udp:180.96.87.24:8080
[2019-08-15 23:13:09.918] [info] 2019/08/15 23:13:09 [Info] [2520382334] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:123.151.144.43:8000]
2019/08/15 23:13:09 [Info] [2520382334] v2ray.com/core/proxy/freedom: opening connection to udp:123.151.144.43:8000
2019/08/15 23:13:09 [Info] [2960548431] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:180.96.87.24:8080]
2019/08/15 23:13:09 [Info] [2960548431] v2ray.com/core/proxy/freedom: opening connection to udp:180.96.87.24:8080
[2019-08-15 23:13:09.937] [info] 2019/08/15 23:13:09 [] [udp] [unknown process] udp:180.96.87.24:8080
[2019-08-15 23:13:09.942] [info] 2019/08/15 23:13:09 [Info] [3001642629] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:180.96.87.24:8080]
2019/08/15 23:13:09 [Info] [3001642629] v2ray.com/core/proxy/freedom: opening connection to udp:180.96.87.24:8080
[2019-08-15 23:13:09.956] [info] 2019/08/15 23:13:09 [] [udp] [unknown process] udp:180.96.87.24:8080
2019/08/15 23:13:09 [] [udp] [unknown process] udp:180.96.87.24:8080
[2019-08-15 23:13:09.957] [info] 2019/08/15 23:13:09 [Info] [2282693903] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:180.96.87.24:8080]
2019/08/15 23:13:09 [Info] [2282693903] v2ray.com/core/proxy/freedom: opening connection to udp:180.96.87.24:8080
2019/08/15 23:13:09 [Info] [1163211201] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:180.96.87.24:8080]
2019/08/15 23:13:09 [Info] [1163211201] v2ray.com/core/proxy/freedom: opening connection to udp:180.96.87.24:8080
2019/08/15 23:13:09 [Info] [698972855] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:180.96.87.24:8080]
2019/08/15 23:13:09 [Info] [698972855] v2ray.com/core/proxy/freedom: opening connection to udp:180.96.87.24:8080
2019/08/15 23:13:09 [Info] [2267027322] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:180.96.87.24:8080]
2019/08/15 23:13:09 [Info] [2267027322] v2ray.com/core/proxy/freedom: opening connection to udp:180.96.87.24:8080
2019/08/15 23:13:09 [Info] [170958641] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:180.96.87.24:8080]
2019/08/15 23:13:09 [Info] [170958641] v2ray.com/core/proxy/freedom: opening connection to udp:180.96.87.24:8080
[2019-08-15 23:13:09.959] [info] 2019/08/15 23:13:09 [] [udp] [unknown process] udp:180.96.87.24:8080
2019/08/15 23:13:09 [] [udp] [unknown process] udp:180.96.87.24:8080
2019/08/15 23:13:09 [] [udp] [unknown process] udp:180.96.87.24:8080
2019/08/15 23:13:09 [] [udp] [unknown process] udp:180.96.87.24:8080
2019/08/15 23:13:09 [] [udp] [unknown process] udp:123.151.144.43:8000
2019/08/15 23:13:09 [] [udp] [unknown process] udp:180.96.87.24:8080 clash日志2019/08/15 23:13:09:000 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:094 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:094 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:096 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:121 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:123 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:126 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:128 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:129 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:132 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:137 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:157 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:168 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:196 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:205 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:217 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:317 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:317 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:331 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:400 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:407 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:414 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:515 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:517 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:517 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:912 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:918 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:921 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:921 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:923 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:926 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:930 [info] 192.168.0.124 --> 180.96.87.24 match GEOIP using DIRECT
2019/08/15 23:13:09:932 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:939 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:944 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:944 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:945 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:945 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:945 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT
2019/08/15 23:13:09:946 [info] 192.168.0.124 --> 123.151.144.43 match GEOIP using DIRECT |
j基本上就是clash的问题。
|
是clash的问题 随着此pr的合并,测试了一下微信视频没有问题。 |
我这里遇到了类似的问题。 异常停止日志
|
在没有微信视频时(也就是不存在大量udp流量的情况下),一切工作正常,一旦视频,cpu占用爆炸,直接没网。
版本信息
配置文件
日志
log.log
The text was updated successfully, but these errors were encountered: