uber/autodispose

Automatic binding+disposal of RxJava streams.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 4 minutes ago
Added to GitGenius on September 20th, 2026
Created on December 22nd, 2016
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 229
Total Stargazers: 3,343 (+0)
Total Subscribers: 66 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

AutoDispose is a library that automatically binds and disposes of RxJava streams.

In reactive programming with RxJava, subscriptions must be explicitly disposed to prevent memory leaks and resource exhaustion. AutoDispose solves this by automating the binding and disposal of streams to lifecycle events. The tool integrates with Android lifecycle components and other lifecycle-aware systems, allowing developers to attach disposal logic directly to lifecycle boundaries without manual subscription management. This approach eliminates the boilerplate of tracking subscriptions and manually calling dispose in lifecycle callbacks.

Developers working with RxJava in Android applications should consider AutoDispose when managing reactive streams across components with defined lifecycles. The library is particularly suited for projects that already use RxJava and want to reduce memory leak risks and subscription management overhead. It works with Kotlin and integrates with reactive extensions and reactive streams patterns, making it applicable to codebases that embrace reactive programming paradigms.

The project shows consistent maintenance with regular updates addressing issues and improvements to the codebase. Development activity demonstrates ongoing engagement with bug fixes and enhancements to core functionality. The maintainers actively respond to and resolve reported issues, indicating sustained support for the library's stability and compatibility.