执行 xray api rmrules 时 CPU 和内存开销均飙升至 100%

[asbai]

完整性要求

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

描述

调用 api adrules 后，再调用 rmrules 或 lsrules 均会引发 CPU 和内存 100%。

重现方式

1. systemctl restart xray

2. xray api adrules << EOF
   {
   "routing": {
   "rules": [
   {
   "tag": "rule-2222",
   "type": "field",
   "inboundTag": ["in-2222"],
   "outboundTag": "out-2222"
   }
   ]
   }
   }
   EOF

3. xray api rmrules 'rule-2222'

执行第 3 步后 CPU 和内存均 100%

xray version
Xray 26.2.6 (Xray, Penetrates Everything.) 12ee51e (go1.25.7 linux/amd64)
A unified platform for anti-censorship.

客户端配置

无

服务端配置

{
"log": {
"loglevel": "warning"
},
"api": {
"tag": "api",
"services": [
"HandlerService",
"RoutingService"
]
},
"inbounds": [
{
"listen": "127.0.0.1",
"port": 8080,
"protocol": "dokodemo-door",
"settings": { "address": "127.0.0.1" },
"tag": "api-in"
}
],
"outbounds": [
{
"tag": "out-direct",
"protocol": "freedom",
"settings": {}
},
{
"tag": "block-out",
"protocol": "blackhole",
"settings": {}
}
],
"routing": {
"rules": [
{ "inboundTag": ["api-in"], "outboundTag": "api", "type": "field" }
]
}
}

客户端日志

无

服务端日志

Feb 22 06:25:03 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:03.995664 from 127.0.0.1:15758 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:03 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:03.996028 from 127.0.0.1:15770 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:03 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:03.996312 from 127.0.0.1:15776 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:03 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:03.996609 from 127.0.0.1:15782 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:03 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:03.996891 from 127.0.0.1:15802 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:03 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:03.997349 from 127.0.0.1:15804 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:03 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:03.997632 from 127.0.0.1:15818 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:03 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:03.997949 from 127.0.0.1:15832 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:03 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:03.998239 from 127.0.0.1:15834 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:03 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:03.998533 from 127.0.0.1:15836 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:03 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:03.998801 from 127.0.0.1:15852 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:03 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:03.999215 from 127.0.0.1:15858 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:03 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:03.999626 from 127.0.0.1:15860 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:03 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:03.999914 from 127.0.0.1:15876 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.000220 from 127.0.0.1:15878 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.000507 from 127.0.0.1:15894 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.000820 from 127.0.0.1:15908 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.001130 from 127.0.0.1:15922 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.001429 from 127.0.0.1:15944 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.001704 from 127.0.0.1:15946 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.001976 from 127.0.0.1:15954 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.002284 from 127.0.0.1:15966 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.002599 from 127.0.0.1:15978 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.002878 from 127.0.0.1:15992 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.003151 from 127.0.0.1:16000 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.003464 from 127.0.0.1:16020 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.003805 from 127.0.0.1:16022 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.004082 from 127.0.0.1:16044 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.004368 from 127.0.0.1:16046 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.004653 from 127.0.0.1:16058 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.004916 from 127.0.0.1:16064 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.005195 from 127.0.0.1:16072 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.005476 from 127.0.0.1:16086 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.005771 from 127.0.0.1:16092 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.006050 from 127.0.0.1:16098 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]
Feb 22 06:25:04 AZ-ZY-G0-SGr2 xray[150297]: 2026/02/22 06:25:04.006333 from 127.0.0.1:16112 accepted tcp:127.0.0.1:8080 [api-in >> out-direct]

[Fangliding]

adrules 默认是替换整个路由 你添加的规则把 api-in → api 的路由覆盖了 而且你还在任意门设置了127.0.0.1 导致任意门直接进 freedom freedom又进入任意门 回环导致吃满cpu 要使用 -append 来设置为追加

不过归根结底是 #3189 PR设计的有问题 看起来它的最初目的就是为了去重载路由规则 没有考虑到这样简单的单条命令不符合直觉的问题 有没有必要 break 把默认 override 可选 append 改成默认 append 可选 override 不过就像我之前说的一样路由规则是个强顺序列表 和 inbounds/users 纯集合随便加减不一样 哪怕是默认 append 如果先rm再ad也会不符合直觉。。

[asbai]

adrules 默认是替换整个路由 你添加的规则把 api-in → api 的路由覆盖了 而且你还在任意门设置了127.0.0.1 导致任意门直接进 freedom freedom又进入任意门 回环导致吃满cpu 要使用 -append 来设置为追加

不过归根结底是 #3189 PR设计的有问题 看起来它的最初目的就是为了去重载路由规则 没有考虑到这样简单的单条命令不符合直觉的问题 有没有必要 break 把默认 override 可选 append 改成默认 append 可选 override 不过就像我之前说的一样路由规则是个强顺序列表 和 inbounds/users 纯集合随便加减不一样 哪怕是默认 append 如果先rm再ad也会不符合直觉。。

感谢提点，确实，如果 API 名字中的谓语为 Add，则默认增量追加更合理一些。否则叫 Update 或者 Replace 可能更合适。

[asbai]

仍然有些问题：

xray api adrules -append << EOF
{
  "routing": {
    "rules": [
      {
        "tag": "rule-2222",
        "type": "field",
        "inboundTag": ["in-2222"],
        "outboundTag": "out-2222"
      }
    ]
  }
}
EOF
reading from stdin:
{}

添加成功后查看：

xray api lsrules
{
    "rules": [
        {
            "tag": "api"
        },
        {
            "tag": "out-2222"
        }
    ]
}

tag 从指定的 rule-2222 变成了 out-2222。

然后，执行：

xray api rmrules rule-2222
{}
# 以及：
xray api rmrules out-2222
{}

后，再 lsrules:

xray api lsrules
{
    "rules": [
        {
            "tag": "api"
        },
        {
            "tag": "out-2222"
        }
    ]
}

规则仍然没有被删除

[asbai]

日志中没有发现与此相关的信息：

Feb 22 17:22:32 AZ-ZY-G0-SGr2 xray[151438]: Xray 26.2.6 (Xray, Penetrates Everything.) 12ee51e (go1.25.7 linux/amd64)
Feb 22 17:22:32 AZ-ZY-G0-SGr2 xray[151438]: A unified platform for anti-censorship.
Feb 22 17:22:32 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:32.336533 [Info] infra/conf/serial: Reading config: &{Name:/usr/local/etc/xray/config.json Format:json}
Feb 22 17:22:32 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:32.336763 [Debug] app/log: Logger started
Feb 22 17:22:32 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:32.336775 [Debug] app/proxyman/inbound: creating stream worker on 127.0.0.1:8080
Feb 22 17:22:32 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:32.336780 [Info] transport/internet/tcp: listening TCP on 127.0.0.1:8080
Feb 22 17:22:32 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:32.336783 [Warning] core: Xray 26.2.6 started
Feb 22 17:22:40 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:40.692845 [Debug] [1211819455] proxy/dokodemo: processing connection from: 127.0.0.1:32980
Feb 22 17:22:40 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:40.692863 [Info] [1211819455] proxy/dokodemo: received request for 127.0.0.1:32980
Feb 22 17:22:40 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:40.692870 [Info] [1211819455] app/dispatcher: taking detour [api] for [tcp:127.0.0.1:8080]
Feb 22 17:22:40 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:40.692919 from 127.0.0.1:32980 accepted tcp:127.0.0.1:8080 [api-in -> api]
Feb 22 17:22:45 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:45.108242 [Debug] [669330530] proxy/dokodemo: processing connection from: 127.0.0.1:32994
Feb 22 17:22:45 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:45.108255 [Info] [669330530] proxy/dokodemo: received request for 127.0.0.1:32994
Feb 22 17:22:45 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:45.108260 [Info] [669330530] app/dispatcher: taking detour [api] for [tcp:127.0.0.1:8080]
Feb 22 17:22:45 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:45.108265 from 127.0.0.1:32994 accepted tcp:127.0.0.1:8080 [api-in -> api]
Feb 22 17:22:55 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:55.826013 [Debug] [2190705975] proxy/dokodemo: processing connection from: 127.0.0.1:59140
Feb 22 17:22:55 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:55.826025 [Info] [2190705975] proxy/dokodemo: received request for 127.0.0.1:59140
Feb 22 17:22:55 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:55.826030 [Info] [2190705975] app/dispatcher: taking detour [api] for [tcp:127.0.0.1:8080]
Feb 22 17:22:55 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:55.826035 from 127.0.0.1:59140 accepted tcp:127.0.0.1:8080 [api-in -> api]
Feb 22 17:22:59 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:59.249798 [Debug] [32553626] proxy/dokodemo: processing connection from: 127.0.0.1:24358
Feb 22 17:22:59 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:59.249810 [Info] [32553626] proxy/dokodemo: received request for 127.0.0.1:24358
Feb 22 17:22:59 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:59.249815 [Info] [32553626] app/dispatcher: taking detour [api] for [tcp:127.0.0.1:8080]
Feb 22 17:22:59 AZ-ZY-G0-SGr2 xray[151438]: 2026/02/22 17:22:59.249835 from 127.0.0.1:24358 accepted tcp:127.0.0.1:8080 [api-in -> api]

[Fangliding]

这个tag是 outboundTag 目标
标识tag名字的字段是ruleTag help 里写的 Remove routing rules by ruleTag from Xray. 啊

[asbai]

这个tag是 outboundTag 目标 标识tag名字的字段是ruleTag help 里写的 Remove routing rules by ruleTag from Xray. 啊

我的错，刚重新学习完文档 https://xtls.github.io/config/routing.html#ruleobject 后就看到你回复了，sorry