-
Notifications
You must be signed in to change notification settings - Fork 4k
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
vless tls server crash with "fatal error: concurrent map writes" #3904
Comments
apt config |
Thank for reporting. Try the version here https://github.com/XTLS/Xray-core/actions/runs/11303197293 for your server |
Ok, I will try it on server from now. |
I can see below errors occasionally. Does this mean the issue is successfully mitigated?
|
Yes, mitigate |
Ok, I'm fine for now. |
I would keep this issue open until the actual bug is fixed. Things are potentially getting mis-routed under mux.cool. |
客户端出现规律的日志: |
Integrity requirements
Description
xray server crash when I do 'apt update' using vless + tls
I don't think I ever see this issue before v24. After I start using v24.9.30, I begin see such crash occasionally on my vps server.
This seems to be a timing issue, not always reproducible, but with time, you can reproduce it.
Reproduction Method
start 3 terminals
terminal 1: (xray server)
xray run -config ./config.json
terminal 2: (xray client)
xray run -config ./config.json
terminal 3: (do apt update with loop, in case you don't have env, my example is using docker/podman to reproduce)
docker run -ti --rm --network host ubuntu:noble bash
cat << \EOF | tee /etc/apt/apt.conf.d/99z-custom
Acquire::Queue-Mode "host";
Acquire::http { Pipeline-Depth "200"; }
Acquire::http::Proxy "http://127.0.0.1:8080";
Acquire::https::Proxy "http://127.0.0.1:8080";
EOF
while :; do apt update && sleep 60 || break ; done
Client config
Server config
Client log
Server log
The text was updated successfully, but these errors were encountered: