go-rabbitmq icon indicating copy to clipboard operation
go-rabbitmq copied to clipboard

memory leak

Open lmb1113 opened this issue 6 months ago • 18 comments

image

image

My English is not very good, please understand.As the concurrency of my project increases, the memory also increases. After investigation, it was found that the reason was due to the publisher.startNotifyBlockedHandler() method's failure to exit and release memory in a timely manner. I am not sure what happened that caused the failure to exit. My expected outcome is publisher Close() can close normally.

After commenting out this line of code, I found it to be effective, but it is not elegant. image

lmb1113 avatar Dec 21 '23 03:12 lmb1113