There are several leaks: - Using `removeRow()` family methods to remove one or multiple rows does not deallocate associated controller and the row itself. - Moreover `removeArrangedSubview()` is not called to remove the view from the stackview along with classic `removeSuperview()`. - Finally the `prevVisibilityState` of the `ScrollStackRow` class keep alive the row once removed.
There are several leaks:
removeRow()family methods to remove one or multiple rows does not deallocate associated controller and the row itself.removeArrangedSubview()is not called to remove the view from the stackview along with classicremoveSuperview().prevVisibilityStateof theScrollStackRowclass keep alive the row once removed.