-
Notifications
You must be signed in to change notification settings - Fork 227
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
Memory leak in daemon #699
Comments
Signed-off-by: Alexey Ryazanov <a.ryazanov@corp.mail.ru> * Update v2/protocol/http/protocol_retry.go
Fix memoty leak(cloudevents#699)
thanks! I will look into this and the linked PR |
I think this was fixed by #689, but we have not had a chance to make a release yet. Could you try your test again with what is at HEAD? |
It looks like it really fixing it. I just tested on snipped code from this issue. I will test tomorrow on my project daemon code. |
Ok awesome, I will wait for you to confirm and then run a release tomorrow. Thanks for the report!! |
All fine. The code from the latest main branch works as expected. All read/write goroutines are closed. No memory leak or overhead memory limit using. Thanks for fast answer, we need it release for our production using. |
awesome, will make a release then, thanks! |
Hi,
we are using client send in daemon and we have memory leak. During debug I found next
Example of code
If I sending 500 request in example in debug goruitine we will see 1000 not close gorutine 500 for read 500 for write
http://localhost:6060/debug/pprof/goroutine?debug=1
for fix this problem need to close Body.Close() https://github.com/cloudevents/sdk-go/blob/main/v2/protocol/http/protocol_retry.go#L36
example
The text was updated successfully, but these errors were encountered: