SagerNet / SagerNet/sing-box

偶尔出现painc导致进程退出

Open
#4,032 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
38.2k
Forks
4.6k
Avg merge
19d 15h
Merged PRs (30d)
1

Description

Operating system

Windows

System version

win11 25H2(Microsoft Windows [版本 10.0.26200.8117])

Installation type

Original sing-box Command Line

If you are using a graphical client, please provide the version of the client.

No response

Version
sing-box version 1.13.7

Environment: go1.25.8 windows/amd64
Tags: with_gvisor,with_quic,with_dhcp,with_wireguard,with_utls,with_acme,with_clash_api,with_tailscale,with_ccm,with_ocm,with_naive_outbound,with_purego,badlinkname,tfogo_checklinkname0
Revision: 025b947a24cf4cba30ca3e629b2a326d1d02e93e
CGO: disabled
Description

之前的版本也会偶尔出现painc,平时记得好像没出现过painc,有几次都是打DNF游戏中出现了,游戏掉线。一看就是sing-box painc了。感觉都是打2-3小时出现的。很诡异。

Reproduction

偶尔出现,比较诡异,painc堆栈日志太大,用文件放这里吧

err.log

Logs

Supporter
Integrity requirements
  • I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
  • I confirm that I have provided the server and client configuration files and process that can be reproduced locally, instead of a complicated client configuration file that has been stripped of sensitive data.
  • I confirm that I have provided the simplest configuration that can be used to reproduce the error I reported, instead of depending on remote servers, TUN, graphical interface clients, or other closed-source software.
  • I confirm that I have provided the complete configuration files and logs, rather than just providing parts I think are useful out of confidence in my own intelligence.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the attached err.log and compare its panic stack with the reported sing-box 1.13.7 Windows environment. Trace the named entry points and relevant Windows process paths, then determine a reproducible trigger or a specific failure cause; done means the intermittent panic is explained and a regression test or validated fix is identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.