【问题标题】:WeakEventManager holds reference to subscriberWeakEventManager 持有对订阅者的引用
【发布时间】:2013-03-05 13:54:08
【问题描述】:

我一直在使用 Wea​​kEventManager 来避免内存泄漏,但我开始过度使用它们。 例如,我为 INotifyPropertyChanged 创建了扩展方法,例如:


public static void AddWeakPropertyChanged(this INotifyPropertyChanged item, Action handler)
{
    PropertyChangedEventManager.AddHandler(item, (s, e) => handler(e.PropertyName), string.Empty);
}

现在我很快意识到,这行不通。事实上,你不能真正使用匿名方法来处理弱事件。 (如果我理解正确,那么编译器会为它创建一个“闭包类”(保存引用的值),它具有处理程序,但由于您的闭包类没有在任何地方引用,GC 会将其清除,并且事件处理程序不会被调用)

问题 #1:正确吗?我的意思是它是否正确,那么当对弱事件处理程序使用匿名方法(或 lambda)时,只有当 GC 没有同时运行时才会调用处理程序(例如它是不确定的)?

嗯,我是这么想的,所以我做了一些单元测试以确保我做对了。在我进行以下单元测试之前,它似乎没问题:


        class DidRun
        {
            public bool Value { get; set; }
        }
        class TestEventPublisher
        {
            public event EventHandler<EventArgs> MyEvent;
            public void RaiseMyEvent()
            {
                if (MyEvent != null)
                    MyEvent(this, EventArgs.Empty);

            }
        }
        class TestClosure
        {
            public DidRun didRun { get; set; }
            public EventHandler<EventArgs> Handler { get; private set; }
            public TestClosure()
            {
                this.Handler = new EventHandler<EventArgs>((s, e) => didRun.Value = true);
            }
        }
        [TestMethod]
        public void TestWeakReference()
        {
            var raiser = new TestEventPublisher();
            var didrun = new DidRun();
            var closure = new TestClosure { didRun = didrun };
            WeakEventManager<TestEventPublisher, EventArgs>.AddHandler(raiser, "MyEvent", closure.Handler);
            closure = null;

            GC.Collect();
            GC.Collect();
            raiser.RaiseMyEvent();
            Assert.AreEqual(false, didrun.Value);
        }

问题 #2:谁能解释我为什么这个测试失败了?

期望:这里我没有任何闭包(我把它们拿出来,以确保发生了什么),我只是有一个对象(闭包),它使用 Wea​​kEventManager 订阅一个事件,然后我删除了引用到它(closure = null;)。

我期待 2 次 GC.Collect() 调用来清理我的旧闭包类,因此 WeakEventManager 将删除订阅者,而不运行处理程序,但测试失败。有什么想法吗?

编辑:对不起,通用参数不可见,现在它们是

【问题讨论】:

    标签: c# closures weakeventmanager


    【解决方案1】:

    如果没有对它的引用,GC 将收集围绕您的 lambda 创建的闭包是正确的。

    在您的单元测试中,您将 TestClosure 的本地实例清空,但您已将处理程序的硬引用传递给 WeakEventManager,而不是 TestClosure 的实例。所以处理程序继续存在......

    我相信这些例子说明了你在关闭时遇到的麻烦:

    class DidRun
    {
        public bool Value { get; set; }
    }
    
    class TestEventPublisher
    {
        public event EventHandler<EventArgs> MyEvent;
        public void RaiseMyEvent()
        {
            if (MyEvent != null)
                MyEvent(this, EventArgs.Empty);
        }
    }
    
    class TestClosure
    {
        static public EventHandler<EventArgs> Register(TestEventPublisher raiser, DidRun didrun)
        {
            EventHandler<EventArgs> handler = (s, e) => didrun.Value = true;
            WeakEventManager<TestEventPublisher, EventArgs>.AddHandler(raiser, "MyEvent", handler);
            return handler;
        }
    }
    
    [TestMethod]
    public void Test1()
    {
        var raiser = new TestEventPublisher();
        var didrun = new DidRun();
    
        TestClosure.Register(raiser, didrun);
    
        // The reference to the closure 'handler' is not being held,
        //  it may or may not be GC'd (indeterminate result)
    
        raiser.RaiseMyEvent();
        Assert.IsTrue(didrun.Value);
    }
    
    [TestMethod]
    public void Test2()
    {
        var raiser = new TestEventPublisher();
        var didrun = new DidRun();
    
        // The reference to the closure 'handler' is not being held, it's GC'd
        TestClosure.Register(raiser, didrun);
    
        GC.Collect();
        GC.Collect();
    
        raiser.RaiseMyEvent();
        Assert.IsFalse(didrun.Value);
    }
    
    [TestMethod]
    public void Test3()
    {
        var raiser = new TestEventPublisher();
        var didrun = new DidRun();
    
        // Keep local copy of handler to prevent it from being GC'd
        var handler = TestClosure.Register(raiser, didrun);
    
        GC.Collect();
        GC.Collect();
    
        raiser.RaiseMyEvent();
        Assert.IsTrue(didrun.Value);
    }
    

    至于您的原始问题,您可以尝试保存处理程序(关闭)以防止它被 GC'd。 ConditionalWeakTable 应该适用于此:

    // ConditionalWeakTable will hold the 'value' as long as the 'key' is not marked for GC
    static private ConditionalWeakTable<INotifyPropertyChanged, EventHandler<PropertyChangedEventArgs>> _eventMapping =
      new ConditionalWeakTable<INotifyPropertyChanged, EventHandler<PropertyChangedEventArgs>>();
    
    public static void AddWeakPropertyChanged(this INotifyPropertyChanged item, Action<string> handlerAction)
    {
        EventHandler<PropertyChangedEventArgs> handler;
    
        // Remove any existing handler for this item in case it's registered more than once
        if (_eventMapping.TryGetValue(item, out handler))
        {   
            _eventMapping.Remove(item);
            PropertyChangedEventManager.RemoveHandler(item, handler, string.Empty);
        }   
    
        handler = (s, e) => handlerAction(e.PropertyName);
    
        // Save handler (closure) to prevent GC
        _eventMapping.Add(item, handler);
    
        PropertyChangedEventManager.AddHandler(item, handler, string.Empty);
    }
    
    class DidRun
    {
        static public string Value { get; private set; }
        public void SetValue(string value) { Value = value; }
    }
    
    [TestMethod]
    public void Test4()
    {
        var property = new ObservableObject<string>();
    
        var didrun = new DidRun();
        property.AddWeakPropertyChanged(
            (x) => 
            {
                didrun.SetValue("Property Name = " + x);
            });
    
        GC.Collect();
        GC.Collect();
    
        property.Value = "Hello World";
    
        Assert.IsTrue(DidRun.Value != null);
    }
    

    【讨论】:

    • 哇,非常感谢,我对此感到困惑,实际上我忽略了,传入的值是对处理程序的硬引用。现在我明白了。再次感谢您的帮助!!!
    • 这同样适用于本地方法,即它们也不能用作事件处理程序,原因基本相同。
    猜你喜欢
    • 2017-01-24
    • 2017-10-31
    • 2016-02-20
    • 2014-10-12
    • 2017-11-08
    • 1970-01-01
    • 2019-01-08
    • 2015-09-01
    • 1970-01-01
    相关资源
    最近更新 更多