-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
[Bug] Error: TCP close of closed channel #1869
Comments
Another log from the crash at a different time: Logcat
|
How have you got the "don't panic" code? Btw, we've since fixed this bug: celzero/firestack#64 |
That's great to see, thanks! It's unfortunate that this bugfix was implemented a few days after v0.5.5n released in June last year and there isn't any bugfix release after that 😅 Unlucky timing, but good to see that this will be fixed whenever a new version is ready to ship. By the way, if the project would benefit from building or improving some CI/CD pipelines for faster bugfix and feature delivery, I may be able to look into it and try to help :) Just let me know.
Isn't this just part of the log? I can confirm that it's not in all of my crash logs from the app though. |
Thanks. Things are almost there. A few tweaks and it may start working. https://github.com/celzero/rethink-app/blob/c4d314f2194721de9ed054b006bc48571dcbf68c/.github/workflows/nightly.yml
Yeah, but I don't think we ever released the "dontpanic" portions...? May be I misremember. A looooong time has passed since the last release. |
When I get time (no promises), I may have a look at it and see what could be fixed/improved :)
I am using the latest stable build v055n |
No any kind of tests 🥶
Sure. Thanks.
Kind of you to include the qualifier, "stable" (: |
(closing this bug as dup, feel free to ask us to reopen) |
Bug description
Sometimes, I believe this is happening when the wifi switches from one network to another one (not 100% sure), the RethinkDNS background process crashes. This leaves the device without any block lists or firewall, which is rather bad for obvious leakage reasons.
Upon observing multiple logs, I can see the error
E GoLog : chan.go:365: E tcp.forward:a2c6791acad924bd [11] close of closed channel
right before the crash happens. Android does not notify of the crash, I can only see it due to the key symbol in the notification bar which says that the VPN is disconnected.Logs
This is one of the logs I captured:
Logcat
Additional info
The text was updated successfully, but these errors were encountered: