Socket unsubscription to OnMessageReceived throws Exception "A method was called at an unexpected time." about yort.ntp HOT 3 CLOSED

Hi,

Are you using the latest version?

The latest version of the WinRT code for this library does the following;

ExecuteWithSuppressedExceptions(() => socket.MessageReceived -= this.Socket_Completed_Receive);

The ExecuteWithSuppressedExceptions should hide that exception if it occurs (it is intermittent in my experience), so it should not cause a problem. If you have 'break on all exceptions' enabled you might see the exception in the debugger but should be able to ignore it and continue.

I prefer to remove the event handler when possible to avoid potential memory leaks (I am not sure the socket object uses a weak event handler reference). Neither Dispose nor setting our reference to the socket to null are likely to clean up the event handler reference (though I don't know for sure what it's Dispose method does internally), so they don't necessarily solve that issue.

from yort.ntp.

Hi, package 1.0.9 solved the problem.

Thank you

from yort.ntp.

Excellent, thanks for letting me know.

from yort.ntp.