Skip to content
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

Fixes memory leak in HazelcastAsyncMultiMap #85

Closed
wants to merge 1 commit into from

Conversation

tsegismont
Copy link
Contributor

@tsegismont tsegismont commented Jan 10, 2018

Calling ClusterManager.getAsyncMultiMap multiple times can leak memory as the map listener is still registered.

See vert-x3/issues#316

Calling ClusterManager.getAsyncMultiMap multiple times can leak memory has the map listener is still registered.

See vert-x3/issues#316
@tsegismont
Copy link
Contributor Author

@vietj PTAL

@tsegismont tsegismont added this to the 3.5.1 milestone Jan 26, 2018
@vietj vietj modified the milestones: 3.5.1, 3.6.0 Feb 12, 2018
@@ -62,7 +63,7 @@
public HazelcastAsyncMultiMap(Vertx vertx, com.hazelcast.core.MultiMap<K, V> map) {
this.vertx = (VertxInternal) vertx;
this.map = map;
map.addEntryListener(this, true);
listenerRegistrationId = map.addEntryListener(this, true);
Copy link
Contributor

@vietj vietj Sep 20, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't pass this in constructor

@tsegismont tsegismont removed this from the 3.6.0 milestone Sep 28, 2018
@tsegismont
Copy link
Contributor Author

vert-x3/issues#316 closed (won't fix)

@tsegismont tsegismont closed this Sep 28, 2018
@tsegismont tsegismont deleted the asyncmultimap-close branch September 28, 2018 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

None yet

2 participants