kNet icon indicating copy to clipboard operation
kNet copied to clipboard

MessageConnections are not freed when NetworkDialog is open

Open cadaver opened this issue 12 years ago • 2 comments

Due to MessageConnectionTreeItem having a shared ptr to MessageConnection, a connection is never freed even after it closes, when the NetworkDialog is open. In a network client usage, this means leaking connections when performing repeated connection and disconnection.

cadaver avatar Mar 25 '14 12:03 cadaver

The connection leakage in Tundra seemed to disappear after this fix: https://github.com/Adminotech/tundra/commit/1de67f3d2d0131d1d7278603d3366465bdd10c0c

Stinkfist0 avatar Mar 27 '14 15:03 Stinkfist0

By leaking, do you mean actually leaking allocated raw memory pointers? Or leaking network memory sockets after MessageConnections are deleted? Do the MessageConnections properly clean up when all dialogs are closed, i.e. is it just a temporary held-alive reference by the NetworkDialog code, or are you actually seeing that connections stay unclosed indefinitely even after the user closes the dialog?

juj avatar Apr 01 '14 16:04 juj