Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
IOBalancer has a memory leak #6199
IOBalancer keeps references of all the socket reader/writers but when destroying the connection they release the references for only the ones which has endpoints.
It could be seen from the image below that socket writers consume %77 of the total memory after all the connections to hazelcast are destroyed.
we're seeing another memory leak in IOBalancer in v3.6 - Socket readers/writers are building up in LoadTracker.lastEventCounter. They are getting added to the ItemCounter by updateNewWorkingImbalance but the handler is not removed from the ItemCounter when removeHandler is called.
Can we re-open this issue or should I open a new one?