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

When the WebSocket connection is closed, the registrations is not clear! #2446

Closed
wjw465150 opened this issue Jul 5, 2023 · 3 comments
Closed
Labels

Comments

@wjw465150
Copy link

Questions

I Found When the WebSocket connection is closed, the registrations is not clear

Version

Vert.x 4.4.4

Problem Code

In io.vertx.ext.web.handler.sockjs.impl.EventBusBridgeImpl class method clearSocketState,The registrations was not clear after the eventbus consumer was unregister!

Solution

after eventbus consumer was unregister,add registrations.clear();
20230705172305

@wjw465150 wjw465150 added the bug label Jul 5, 2023
@vietj vietj added this to the 4.4.5 milestone Jul 6, 2023
@tsegismont
Copy link
Contributor

I don't believe this is a problem, the map and its entries should be collected after the SockJS socket is closed.

Can demonstrate a leak with a reproducer?

@wjw465150
Copy link
Author

Isn't it good to proactively close and release resources in a timely manner?

@tsegismont
Copy link
Contributor

The resources (message consumers) are closed and released.

What you are talking about is removing references from the map instance to its entries, which are both going to be gc-ed later anyway.

I'm closing the issue but if there's an actual leak which can be demonstrated with a reproducer, feel free to reopen with all the details.

@tsegismont tsegismont closed this as not planned Won't fix, can't repro, duplicate, stale Jul 7, 2023
@tsegismont tsegismont removed the bug label Jul 7, 2023
@tsegismont tsegismont removed this from the 4.4.5 milestone Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants