-
-
Notifications
You must be signed in to change notification settings - Fork 631
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
Deadlock, Goroutines count reaching sky high #820
Comments
Thanks for the report. Are you seeding/uploading a lot? This commit sticks out as a likely candidate: 2cb7121. |
any update on this? 11 days uptime on application and goroutine count reached below stats:
|
Tested, goroutine leak is not there with 1.48.0 + e8971ea |
If you could provide a stack trace that would be amazing! Also if you want to try running with 2cb7121 reverted/reversed out, that will prove it's the issue too. |
The goroutine profile mentioned here https://pkg.go.dev/runtime/pprof#Profile, and exposed via https://pkg.go.dev/net/http/pprof is an easy way to capture that. I have a helper that I use do it if you aren't familiar with it: https://github.com/anacrolix/envpprof. |
@JaskaranSM I believe I have a fix, if the above suspect is indeed the issue. A stack trace would have confirmed it. Please try out this commit: 3c8d702. |
Tested latest dev branch, When I tried to directly go get with the aforementioned commit hash, it resulted in unknown revision error (GitHub says its not attached to a branch and could be from outside the repo), Then I just switched to dev because it had that commit, Here's a quick test's results: |
Thank you! I don't know why doing it the envpprof does it isn't the default. I've been doing it this way for nearly 10 years. |
Can confirm I am observing this issue when running Erigon v2.43.0 which seems to be depending on v1.48.1-0.20230219022425-e8971ea0f1bf Here's what my goroutine pprof looks like: Attaching the pprof file as well (zipped to be a supported file format for github) |
@BriungRi please run after |
@JaskaranSM Thank you very much! |
@JaskaranSM are you using any non-standard transports? The panic you show should only occur with WebRTC or webseeding perhaps. I'll have a fix soon regardless. |
I will tentatively close, this is fixed in dev, and will be in v1.51.0. Let me know if it's not fixed in either of those places! |
@anacrolix hi. is it possible to backport this fix to
|
I just recently restored compatibility with go 1.19 in |
it works, thank you |
This bug was not present in the v1.47 build I was using, However updated the client today as suggested in #813 (comment) , After adding around 10 torrents, the runtime started getting goroutine spikes, smells to be a deadlock caused by new changes
The text was updated successfully, but these errors were encountered: