-
Notifications
You must be signed in to change notification settings - Fork 223
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
fix: connection leaks #624
Conversation
❌ Your branch is currently out-of-sync to main. No worry, I will fix it for you. |
❌ Your branch is currently out-of-sync to main. No worry, I will fix it for you. |
eed06b3
to
2ca199c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧪 Since the PR has been fully tested, please consider merging it.
372a0e9
to
af8c10c
Compare
❌ Your branch is currently out-of-sync to main. No worry, I will fix it for you. |
Co-authored-by: dae-prow[bot] <136105375+dae-prow[bot]@users.noreply.github.com> (cherry picked from commit 218ae3f)
Co-authored-by: dae-prow[bot] <136105375+dae-prow[bot]@users.noreply.github.com>
0.7.4 版本 vless协议不能用 是什么情况 |
@digua-cn 先用 0.8.0 吧 |
Background
Many users have reported continuous memory growth in dae, possibly due to coroutine leaks.
This phenomenon is even more obvious when the network is disconnected. A very suspicious object is that our dialer does not implement DialContext, resulting in the timeout mechanism not being triggered when calling down.
This PR attempts to fix this problem.
Checklist
Full Changelogs
Issue Reference
Closes #[issue number]
Test Result