wodSSHDCom handle leak? (wodSSH / wodSSH.NET)
We're currently in the process of tracking down memory and handle leaks in our application and we've noticed that there appears to be a handle leak when calling Start() and Stop() on wodSSHDCom.
Start() creates two handles named wodCmdTermDesktop , but Stop() only frees one of these handles. If you call Start() and Stop() in a loop you end up with several handle leaks (we don't actually do this, but it proves the case). We noticed this leak using SysInternals Process Explorer.
We're using version 2.2.7.358 of wodSSHD.dll (dated 29/12/2010), so I don't know if this has been fixed in a subsequent release.
Regards,
David Lucas
Data Track Technology
Re: wodSSHDCom handle leak?
David,
Thank you. I believe I managed to reproduce this. We'll check this out and let you know more as soon as our developers look at it.
Regards,
Damba
Re: wodSSHDCom handle leak?
Hi David,
I believe this should now be corrected. Please request an update and try it out.
Regards,
Damba