[Issue #153] Fix handler memory leak#154
Conversation
|
Can you add a test for this? |
|
@freeznet Would you please help handle @cckellogg 's comments? Thanks |
ab6f5a9 to
0a63338
Compare
|
@cckellogg deadlock has been resolved as you mentioned, also add test for |
0a63338 to
7c0563f
Compare
cckellogg
left a comment
There was a problem hiding this comment.
It seems like the tests did not run on the last commit?
pulsar/consumer_impl.go
Outdated
| wg.Wait() | ||
| close(c.closeCh) | ||
| }) | ||
| c.client.handlers.Del(c) |
There was a problem hiding this comment.
Is there a reason not to call this in the closeOnce?
There was a problem hiding this comment.
the initial thought was delete operation will be no-op if consumer/producer not in handlers, so i didnt put Del call in the closeOnce. But your idea is better, which will prevent non necessary locks&unlocks.
@cckellogg the test runs ok on my laptop, can you provide any detail? thanks. |
7c0563f to
eb7ce1e
Compare
|
What happens when you start pulsar in standalone and run Is there a way we can trigger the unit/integration tests? It would be nice to have those run to ensure the issue has been fixed. |
|
retest this please |
Fixes: #153
Makes producer & consumer removed from client handler when producer / consumer closed.