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 protocol dubbo maybe #163
Comments
From pprof file, I got result. Lot of memory used by github.com/apache/dubbo-go/protocol/dubbo.NewPendingResponse function then store the object to sync.Map , but not clean after heatbeat response got. dubbo-go/protocol/dubbo/listener.go Lines 90 to 94 in 9bcb593
|
AlexStocks
added a commit
that referenced
this issue
Aug 14, 2019
[ISSUE #163] clean heartbeat from PendingResponse
AlexStocks
pushed a commit
that referenced
this issue
Aug 14, 2019
cityiron
pushed a commit
that referenced
this issue
Apr 11, 2021
LaurenceLiZhixin
pushed a commit
to LaurenceLiZhixin/dubbo-go
that referenced
this issue
Jul 17, 2021
* add tracing integration test * refactor imports * update metadata service import to local & remote
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
Running for several days with dubbo-go,I see the graphical display of memory of this project, and show this:(The ordinate is the percentage of machine memory, and the machine configuration is 2G memory.)
then I use go pprof to see what is wrong,here is my log:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
I use geneic $invoke and have about 60 interfaces,About 1,000 requests per hour during the day。
show my code :
Anything else we need to know?:
The text was updated successfully, but these errors were encountered: