新的 Reverse 极简配置，在内网端启动的时候报错。

[mclovin-2k]

完整性要求

• 我读完了 issue 模板中的所有注释，确保填写符合要求。
• 我保证阅读了文档，了解所有我编写的配置文件项的含义，而不是大量堆砌看似有用的选项或默认值。
• 我提供了完整的配置文件和日志，而不是出于自己的判断只给出截取的部分。
• 我搜索了 issues, 没有发现已提出的类似问题。
• 问题在 Release 最新的版本上可以成功复现

描述

在内网端，使用 Reverse 极简配置，启动XRAY报错。

重现方式

启动就报错。
只要去掉outbound数组中的Reverse outbound，就可以正常启动。

客户端配置

Details

{
    "outbounds": [
        {
            "tag": "outboundDirect",
            "protocol": "direct",
            "settings": {
                "domainStrategy": "UseIP"
            }
        },
        {
            "tag": "outboundBlock",
            "protocol": "block",
            "settings": {
                "response": {
                    "type": "http"
                }
            }
        },
        {
            "tag": "outboundReverseProtal10",
            "protocol": "vless",
            "settings": {
                "address": "x.x.x.x",
                "port": 443,
                "id": "WorkPC-ReversePortal",
                "flow": "xtls-rprx-vision",
                "encryption": "none",
                "reverse": {
                    "tag": "ReverseProtal10"
                }
            },
            "streamSettings": {
                "network": "raw",
                "security": "reality",
                "realitySettings": {
                    "publicKey": "4ifYtrbCyG8lZQJ47O3Nz3Z9p7q7NFv8MhEm_dbfA04",
                    "serverName": "www.gov.hk"
                }
            }
        }
    ]
}

服务端配置

不涉及服务端

客户端日志

Details

2025/09/10 14:04:22.736673 [Info] transport/internet/tcp: listening TCP on 0.0.0.0:7070
2025/09/10 14:04:23.493912 [Debug] [2941095835] proxy/socks: Not Socks request, try to parse as HTTP request
2025/09/10 14:04:23.494476 [Info] [2941095835] proxy/http: request to Method [CONNECT] Host [mtalk.google.com:5228] with URL [//mtalk.google.com:5228]
2025/09/10 14:04:23.499423 from 10.33.93.249:64438 accepted //mtalk.google.com:5228 [inboundAutoRouting -> outboundProxy]
2025/09/10 14:04:23.823573 [Info] [2941095835] app/dispatcher: sniffed domain: mtalk.google.com
2025/09/10 14:04:23.881437 [Info] [2941095835] app/dispatcher: taking detour [outboundProxy] for [tcp:mtalk.google.com:5228]
2025/09/10 14:04:23.900823 [Info] [2941095835] transport/internet/tcp: dialing TCP to tcp:xxxx:443
2025/09/10 14:04:23.925260 [Debug] [2941095835] transport/internet: dialing to tcp:xxxx:443
2025/09/10 14:04:23.951783 [Info] [2941095835] proxy/vless/outbound: tunneling request to tcp:mtalk.google.com:5228 via xxxxx:443
2025/09/10 14:04:23.967280 [Info] [2941095835] proxy: XtlsFilterTls found tls client hello! 1795
2025/09/10 14:04:23.976806 [Info] [2941095835] proxy: XtlsPadding 1795 109 0
2025/09/10 14:04:24.097627 [Info] [2941095835] proxy: Xtls Unpadding new block, content 2416 padding 13 command 0
2025/09/10 14:04:24.097627 [Info] [2941095835] proxy: XtlsFilterTls inconclusive server hello 1163 52
2025/09/10 14:04:24.121324 [Info] [2941095835] proxy: XtlsFilterTls found tls 1.3! 1253 TLS_AES_128_GCM_SHA256
2025/09/10 14:04:24.125124 [Info] [2941095835] proxy: Xtls Unpadding new block, content 1208 padding 115 command 0
2025/09/10 14:04:24.144795 [Info] [2941095835] proxy: Xtls Unpadding new block, content 4072 padding 198 command 0
2025/09/10 14:04:24.150228 [Info] [2941095835] proxy: XtlsPadding 64 864 0
2025/09/10 14:04:24.171355 [Info] [2941095835] proxy: XtlsPadding 210 1114 2
2025/09/10 14:04:24.309845 [Info] [2941095835] proxy: Xtls Unpadding new block, content 537 padding 817 command 2
2025/09/10 14:04:24.309845 [Info] [2941095835] proxy: CopyRawConn (maybe) readv
2025/09/10 14:04:24.388552 [Debug] [1253880712] proxy/socks: Not Socks request, try to parse as HTTP request
2025/09/10 14:04:24.389153 [Info] [1253880712] proxy/http: request to Method [CONNECT] Host [mtalk.google.com:5228] with URL [//mtalk.google.com:5228]
2025/09/10 14:04:24.437749 [Info] [1253880712] app/dispatcher: sniffed domain: mtalk.google.com
2025/09/10 14:04:24.437749 from 10.33.93.206:6137 accepted //mtalk.google.com:5228 [inboundAutoRouting -> outboundProxy]
2025/09/10 14:04:24.437749 [Info] [1253880712] app/dispatcher: taking detour [outboundProxy] for [tcp:mtalk.google.com:5228]
2025/09/10 14:04:24.483811 [Info] [1253880712] transport/internet/tcp: dialing TCP to tcp:xxxxx:443
2025/09/10 14:04:24.507764 [Debug] [1253880712] transport/internet: dialing to tcp:xxxxx:443
2025/09/10 14:04:24.514738 [Info] transport/internet/tcp: dialing TCP to tcp:xxxxx:443
2025/09/10 14:04:24.538186 [Info] transport/internet/tcp: dialing TCP to tcp:xxxxxx:443
2025/09/10 14:04:24.572722 [Debug] transport/internet: dialing to tcp:xxxxx:443
2025/09/10 14:04:24.597903 [Debug] transport/internet: dialing to tcp:xxxxxx:443
2025/09/10 14:04:24.667060 [Info] proxy/vless/outbound: tunneling request to unknown: via xxxxx:443
2025/09/10 14:04:24.854408 [Info] [1253880712] proxy/vless/outbound: tunneling request to tcp:mtalk.google.com:5228 via xxxxx:443
2025/09/10 14:04:24.854408 [Info] [1253880712] proxy: XtlsFilterTls found tls client hello! 1763
2025/09/10 14:04:24.859407 [Info] [1253880712] proxy: XtlsPadding 1763 85 0
2025/09/10 14:04:24.950058 [Info] proxy/vless/outbound: tunneling request to unknown: via xxxxx:443
2025/09/10 14:04:25.049302 [Info] [1253880712] proxy: Xtls Unpadding new block, content 1208 padding 162 command 0
2025/09/10 14:04:25.049302 [Info] [1253880712] proxy: XtlsFilterTls inconclusive server hello 1163 52
2025/09/10 14:04:25.088797 [Info] [1253880712] proxy: XtlsFilterTls inconclusive server hello 45 7
2025/09/10 14:04:25.113012 [Info] [1253880712] proxy: Xtls Unpadding new block, content 2416 padding 140 command 0
2025/09/10 14:04:25.118945 [Info] [1253880712] proxy: XtlsFilterTls found tls 1.3! 2416 TLS_AES_128_GCM_SHA256
2025/09/10 14:04:25.145307 [Info] [1253880712] proxy: Xtls Unpadding new block, content 3624 padding 104 command 0
2025/09/10 14:04:25.149016 [Info] [1253880712] proxy: Xtls Unpadding new block, content 449 padding 723 command 0
2025/09/10 14:04:25.177417 [Info] [1253880712] proxy: XtlsPadding 64 950 0
2025/09/10 14:04:25.180732 [Info] [1253880712] proxy: XtlsPadding 209 783 2
2025/09/10 14:04:25.203984 [Info] proxy/vless/outbound: Insert padding with empty content to camouflage VLESS header 0
panic: 2025/09/10 14:04:25.232130 [Info] proxy: XtlsPadding 0 943 0
runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x18 pc=0x7ff6e6d4daac]
goroutine 78 [running]:

2025/09/10 14:04:25.251348 [Info] proxy: Xtls Unpadding new block, content 20 padding 187 command 0

github.com/xtls/xray-core/common/signal.(*ActivityTimer).Update(...)

github.com/xtls/xray-core/common/signal/timer.go:28

github.com/xtls/xray-core/app/reverse.(*BridgeWorker).handleInternalConn(0xc0001c8140, 0xc0003481c0?)

github.com/xtls/xray-core/app/reverse/bridge.go:176 +0x6c

created by github.com/xtls/xray-core/app/reverse.(*BridgeWorker).Dispatch in goroutine 12

github.com/xtls/xray-core/app/reverse/bridge.go:203 +0x745

服务端日志

不涉及服务端

[patterniha]

This was due to a lack of coordination between me and @RPRX (two PRs at the same time), anyway, it was my fault.

fixed in #5119.

it is better to tag "Pre-release" for a few days after adding new-features.

[mclovin-2k]

This was due to a lack of coordination between me and @RPRX (two PRs at the same time), anyway, it was my fault.

fixed in #5119.

it is better to tag "Pre-release" for a few days after adding new-features.

OK I will wait for new release.

[mclovin-2k]

fixed

[RPRX]

与是否 pre 无关，而是代码能跑就不要乱动，我感觉 mux 和 reverse 已经改成一坨了，今年内全改成 dispatchLink() 就好了，说到底为什么会存在可能的 goroutine leak，还不是 *ray 这狗屎架构到处开 pipe，本来串联起来的东西结果变成了一个个独立的 goroutine

[Fangliding]

最近的几个leak好像是去掉一些超时机制后导致的 不是pipe

[RPRX]

我的意思是其实本来事情就很简单，全部用 dispatchLink() 函数调用加 ctx cancel 串起来，只需要有仅一处超时机制就行了，清晰明了

本质上就是滥用 pipe 和追求复杂设计模式的遗毒，恶心死了

[RPRX]

一开始就主按线性模式写代码、没那么多 register、interface、goroutine 啥的就没这么多问题要修，*ray 的架构黑一辈子，啥玩意儿

[RPRX]

反正我是写不出来这些东西，让这种代码继续存在于世间就是全人类的灾难，今年内就全扬了

[RPRX]

还想说些什么被你打断了一时忘了，总之今天只能重发个 911 了，要不是当初 fork 了这一坨谁他妈要维护这些狗屎，简直浪费生命

别的软件我不了解，反正与 *ray 的狗屎架构斗智斗勇就是浪费生命，说实话每次看到有新的开发者进来并浪费时间我都感到心痛

今年内的目标就是把这些垃圾设计模式全部清掉，至少我捏着鼻子并浪费生命干完这件事后，后来的开发者可以节约生命

[patterniha]

Removing tcp-inbound-keepalive and using DispatchLink caused many goroutine leaks(goroutines that waited on inbound-reader).

there is no leak now, but the code messed up with so many redundant timers.

The mux-code implemented keepAlive for mux but it didn't use that.
If we enable that we can remove all other redundant timers.
Then we can also remove reverse-keepalive.

I will try to do this, the code will be significantly simplified.

[RPRX]

时间多的话可以把其它入站也改成 dispatchLink()

Xray-core 的启动方式应改为：

1. 按合理的顺序初始化各个组件，并把它们的指针存到确定的结构体中，不要 features
2. 初始化依赖第一步的完成才能初始化的东西
3. 各个组件开始工作，比如开始处理流量与 API

多 instance 也不需要，但应当加上单连接详情、配置订阅、#5117 等功能