How to solve memory leaks in RxJava?

Unsubscribe from subscriptions.

Use CompositeDisposable to manage subscriptions.

// Create an instance
private val compositeDisposable = CompositeDisposable()

// Add subscription to CompositeDisposable
compositeDisposable.add(
    observable.subscribe(
        { result -> /* handle result */ },
        { error -> /* handle error */ }
    )
)

// Unsubscribe from all subscriptions when destroying the component (e.g., in onDestroy())
override fun onDestroy() {
    super.onDestroy()
    compositeDisposable.dispose()
}

Use operators that manage the lifecycle.

• takeUntil(): Completes the Observable when another Observable emits an item.
• autoDispose() (from RxLifecycle or AutoDispose library): Automatically unsubscribes when the component's lifecycle ends.

Use weak references.

// Example of using WeakReference for Context
WeakReference<Context> contextRef = new WeakReference<>(context);

// Inside subscription, check for a strong reference before use
contextRef.get()?.run {
    // Use Context
}

Be cautious of implicit references, such as in lambdas or anonymous classes, which may capture the context or other long-lived objects.

Avoid creating Observables that never complete unless they are long-term, such as Hot Observables that are expected to emit events continuously.

Use Android Profiler to detect memory leaks.