C#•13mo ago

✅ Implementing IDisposable properly

I have a class I implemented IDisposable in which subscribes to an observable of a type. Example: subscribes to an incoming GenericMessage. I am running into an issue where when an instance of this class should be disposed, it's still alive intercepting data from another class that needs it. Here are my logs for visualization:

[SetResult] Fired for MessageReceiver`1[Messages.GenericMessage]
...
[Dispose] Fired for MessageReceiver`1[Messages.GenericMessage]
...
[SetResult] Fired for MessageReceiver`1[Messages.GenericMessage]
[Fatal] An attempt was made to transition a task to a final state when it had already completed

[SetResult] Fired for MessageReceiver`1[Messages.GenericMessage]
...
[Dispose] Fired for MessageReceiver`1[Messages.GenericMessage]
...
[SetResult] Fired for MessageReceiver`1[Messages.GenericMessage]
[Fatal] An attempt was made to transition a task to a final state when it had already completed

As you see my dispose is called but it's still alive. I am using the dispose design pattern as outlined in the IDisposable docs

15 Replies

Mango•13mo ago

Same result if finalizer is suppresses or not

Sossenbinder•13mo ago

How did you implement it? Disposing an object is not the same as the object being garbage collected, you just free it from any unmanaged resources or event handler / responsibilities until it is eventually collected by the GC So is there a chance you're not cleaning up an event handler in your dispose, and the object keeps doing work?

Mango•13mo ago

https://learn.microsoft.com/en-us/dotnet/standard/garbage-collection/implementing-dispose

Implement a Dispose method

In this article, learn to implement the Dispose method, which releases unmanaged resources used by your code in .NET.

Mango•13mo ago

The dispose pattern section is what I implemented The event isn't class level nor is there an unsubscribe so I need to tell the gc hey destroy this now The event is a subscribe on a Subject<T> for context in a constructor of a class

Sossenbinder•13mo ago

Any chance you got some sample code? Would the object even be cleaned up at this point in time then? Sounds like you have a lingering reference somewhere

Mango•13mo ago

I cannot share my code but I can write an xy snippet This is what I'd like to accomplish, forcing it to be destroyed when dispose is called

Sossenbinder•13mo ago

Not sure if it's a good idea to try to interfere with the GC. Subject<T> sounds like an Rx thing, wouldn't you also receive a handle or could you inject a pipe takeUntil? I only know rxjs in Angular

Mango•13mo ago

public GenericMessage()
{
     _subject.Subscribe(SetResponse);
}

private void SetResponse(GenericMessage message)
{  _taskCSource.SetResult(messsage);
}

public GenericMessage()
{
     _subject.Subscribe(SetResponse);
}

private void SetResponse(GenericMessage message)
{  _taskCSource.SetResult(messsage);
}

Sossenbinder•13mo ago

Is that dotnet reactive?

Mango•13mo ago

Yeah Oh I am so dumb

Sossenbinder•13mo ago

I just looked it up, it seems like subscribe gives you an IDisposable You can dispose in your own dispose

Mango•13mo ago

I forgot Subject<T> implements IDisposable. I just learned the surface of it yesterday Yep

Sossenbinder•13mo ago

👍 That sounds like the way to go then

Mango•13mo ago

Thank ya, rubber ducky moment but was needed

Sossenbinder•13mo ago

Gaming

Programming

✅ Implementing IDisposable properly