riverpod-auto-dispose

To automatically dispose of Riverpod providers and prevent memory leaks, enable autoDispose so providers release resources when they have zero listeners for one frame. You can activate this using codegen annotations or Provider.autoDispose in your Flutter app.

In Riverpod state management, ref.onDispose executes cleanup logic when a provider is destroyed, while ref.keepAlive temporarily preserves provider results to prevent automatic disposal despite having no active listeners.

To configure autoDispose for parameterized Riverpod providers, apply Provider.autoDispose or disable keepAlive in codegen. This avoids infinite caching by ensuring the provider disposes when it loses listeners, managing memory for dynamic arguments.

A Riverpod autoDispose provider triggers resource cleanup after exactly one frame of having zero active listeners. This delayed disposal mechanism ensures resources are released efficiently without interrupting rapid UI rebuilds during navigation.

Yes, you can force the disposal and state invalidation of a Riverpod provider manually by calling ref.invalidate. This triggers the ref.onDispose lifecycle hook and destroys the current state, forcing a fresh computation on the next read.

Yes, Riverpod code generation enables autoDispose by default when the keepAlive parameter is not specified or set to false. This ensures automatic resource cleanup occurs unless you explicitly override the lifecycle behavior.