Question about Signal leak / memory managment about reactiveswift

[andersio]

If you obtain a reference to the produced signal, it does turn nil after completion.

This is caused by a caveat of Swift's ref-counting implementation: while the object is deinitialized after its last strong reference is ceased, the object would not be freed until all its weak references have been touched.

If you do not retain the cancel disposable, which indirectly holds a weak reference to the signal, Instruments would no longer catch this leak.

https://github.com/apple/swift/blob/master/docs/weak.rst#implementation
(Despite not being updated post-1.0, Swift's ref counting still works this way)

However, it does have a very important downside: since the system cannot clear all the references, it is impossible to actually deallocate an object that is still weakly-referenced (although it can be finalized). Instead, the system must wait for all the weak references to at least be accessed. We call this "husk leaking".

[emuye]

@andersio Thanks for responding so quicky. Can you show me the code for seeing the reference go to nil after completion?

[andersio]

Instruments caught a leak. But the signal is freed after accessing the weak signal property (which gives you a nil), or when self deinitializes.

    weak var signal: Signal<(), NoError>?
    @IBAction func buttonTouchedUpInside(_ sender: Any) {
       SignalProducer<(), NoError>.empty.startWithSignal { signal, _ 
           self.signal = signal
       }
    }

No leak was caught.

    @IBAction func buttonTouchedUpInside(_ sender: Any) {
       SignalProducer<(), NoError>.empty.startWithCompleted {}
    }

Instruments caught a leak, but the signal should be freed after the disposable is thrown away.

    var disposable: Disposable?
    @IBAction func buttonTouchedUpInside(_ sender: Any) {
       disposable = SignalProducer<(), NoError>.empty.startWithCompleted {}
    }