Gemini WebSocket disconnect doesn't shutdown nioEventLoopGroup threads
KeshavSirohi opened this issue · 3 comments
KeshavSirohi commented
Gemini disconnect doesn't shutdown nioEventLoopGroup threads. When re-connection(disconnect and then connect) is done, two new nioEventLoopGroup threads gets created. This count keeps on increasing because older threads never shutdown.
badgerwithagun commented
Could you try the code on pull request #282?
That tries to be more thorough at shutting down the event loop group in all cases.
KeshavSirohi commented
Issue remains with PR 282. I think the issue is in Gemini classes.
badgerwithagun commented
I did a full tidy-up of this are in #340. Looks like it should help.