WeakPropertyBridge.CheckForUnsubscribe

Sep 19, 2011 at 2:20 PM

I am chasing memory leaks on my app, and noticed there are quite a few related to ReactiveObject. In looking at WeakPropertyBridge.CheckForUnsubscribe, I noticed that calls to it are commented out, and not maitained for a while (they don't compile correctly anymore in uncommented). What is the reason for the call to be commented out? Is there any other place in the code that is doing that job? Is doesn't look like it to me...