Memory leaks from missed resource disposal

7/10 High

Controllers and streams (AnimationController, TextEditingController, ScrollController, FocusNode, StreamSubscription) allocate resources that Dart's garbage collector doesn't automatically clean up. If not manually disposed, they remain in memory after their widgets are destroyed, causing memory leaks in long-running apps.

FlutterDart
Category
performance
Workaround
solid
Stage
debug
Freshness
persistent
Scope
framework
Recurring
Yes

Sources

Collection History

Query: “What are the most common pain points with Flutter for developers in 2025?”4/4/2026

Some classes in Flutter allocate resources that Dart's garbage collector doesn't automatically clean up. These include AnimationController, TextEditingController, ScrollController, FocusNode, and StreamSubscription. If these aren't disposed manually, they remain in memory even after the widget that created them is gone.

Created: 4/4/2026Updated: 4/4/2026