rxswift-memory-check

Memory leaks in RxSwift occur when subscriptions aren't properly disposed or hold strong references to `self`. Detect them by verifying every `.subscribe()` call uses `.disposed(by: disposeBag)` with a property-level DisposeBag, checking for `[weak self]` in closures, and scanning for local DisposeBag declarations that cause premature cancellation. Tools that analyze subscription patterns and flag retain cycles pinpoint exact leak locations with remediation guidance.

Retain cycles occur when Observable chains capture strong `self` references without `[weak self]` or `[unowned self]` capture lists, creating circular references that prevent deallocation. Prevent them by always using weak or unowned captures in subscription closures, ensuring subscriptions are disposed via property-level DisposeBags, and avoiding local DisposeBag instances that dispose prematurely. Static analysis identifies these patterns before they cause memory growth.

Yes—every RxSwift subscription should be disposed by a property-level DisposeBag to prevent memory leaks and ensure proper cleanup. Local DisposeBags dispose immediately when leaving scope, canceling subscriptions prematurely. Property-level DisposeBags tied to object lifecycles ensure subscriptions persist for the intended duration and clean up when the object deallocates.

Strong self references in RxSwift closures (`.subscribe()`, `.map()`, `.flatMap()`) create retain cycles. Find them by scanning for closures that access `self` without `[weak self]` or `[unowned self]` capture lists. Automated analysis flags these locations, shows severity, and provides exact lines where strong captures occur in view models and services, enabling quick remediation.

Property-level DisposeBags are instance variables that persist with the object and dispose subscriptions when the object deallocates—the correct pattern. Local DisposeBags are stack variables that dispose subscriptions immediately when exiting scope, causing premature cancellation and breaking Observable chains. Always use property-level DisposeBags for RxSwift subscriptions.

Yes. Memory leak detection analyzes RxSwift subscriptions across ViewModels, services, and other components by checking disposal patterns, weak/unowned self usage, and DisposeBag placement everywhere subscriptions occur. It generates structured reports showing leak locations, severity, and fixes applicable to your entire RxSwift architecture.