-
Notifications
You must be signed in to change notification settings - Fork 84
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
Not all members in Multicastclient are disposed #93
Comments
I've created pull-request 94 for this. |
@richardschneider : Do you have any chance to take a look at this issue and the corresponding PR since this is a bug that is hurting us. Thanks in advance |
No contributions from @richardschneider for months now, no comments on issues. :( |
We're using a local build as wel ftm, but I'd like to get rid of it sooner then later :) Hope @richardschneider is doing well. |
Maybe we should, since it's almost 6 months since @richardschneider was active on github |
@fgheysels In the meanwhile I also think at least a temporary fork might indeed be a good idea. Are you familiar with GitHub Actions and publishing NuGet packages? |
No, I'm not familiar with GitHub Actions, I mostly use Azure DevOps which also integrates well with Github repos. |
The question remains open, how we would actually do this. |
Should we fork it to a separate GitHub account instead of to one of our personal accounts ? |
I have also neither worked with GitHub Actions, nor published packages to NuGet. So it would more be the "learn something new" approach. ;) Aside from this, I'd also prefer a separate account/organization rather than using our personal accounts. Nevertheless I wrote an email to Richard some minutes ago, just to give him yet another chance to stop us. And maybe we can switch to some other tool or good old email for further disucssions instead of flooding this issue. |
When instantiating a
MulticastService
object, I see that 2UdpClient
instances are created. However, those 2 instances are not disposed when disposing theMulticastService
object. SinceUdpClient
implementsIDisposable
, I believe those 2 instances should be disposed as well ?It seems that not disposing the UdpClient instances causes a memory leak.
The text was updated successfully, but these errors were encountered: