<< All versions

Skill v1.0.1

currentAutomated scan100/100
techmefr/mentis/flutter-dispose-what-you-create

+1 new

──Details
PublishedNovember 7, 2026 at 08:19 AM
Content Hashsha256:ec5ca66661233e79...
Git SHAf2a8e60bba80
Bump Typepatch
Compare with v1.0.0
──Files
Files (1 file, 3.0 KB)
SKILL.md3.0 KBactive
SKILL.md · 49 lines · 3.0 KB

name: flutter-dispose-what-you-create description: "Use when writing or reviewing a widget's dispose(): never dispose a controller you didn't create — a constructor-injected controller belongs to its caller, disposing it there is a double-dispose crash." metadata: version: "1.0.1"


flutter-dispose-what-you-create

Narrow trigger extracted from skills/flutter-conventions §1.12–§1.13, so a widget's dispose() method routes here directly instead of only through the whole Flutter block.

When

Writing or reviewing a widget's dispose() (or a state holder's close()), specifically when the widget also releases a subscription or disposes a controller.

Steps

  1. Never dispose what you didn't create. A controller passed in through the constructor belongs

to the caller; a state holder owned by a provider is closed by that provider. Disposing either here is a double-dispose crash, surfacing in a different file than the one you're reading.

  1. Release in the reverse order of the dependency. Cancel a subscription before disposing the

controller it writes into — otherwise the last callback in flight arrives at a disposed object, and the crash names the controller instead of the listener that was still running.

Output / checkpoint

dispose() only tears down what this widget's initState/late final field created; anything received through the constructor is left untouched. Subscriptions are cancelled before the controllers they write into are disposed.

Guardrails

  • Pairs with flutter-no-controller-in-build — instances hoisted correctly out of build still need

a matching, correctly-ordered teardown here.

  • `dispose` runs even when `initState` didn't finish — if setup threw halfway, teardown still

executes against half-initialised fields, so a late final never assigned throws from dispose and hides the original failure (skills/flutter-conventions §1.15).

Origin

Extracted from skills/flutter-conventions §1.12-§1.13 (written 2026-09-09). Checked 2026-10-20 against the State.dispose API page (release what the object holds; unsubscribe in dispose what was subscribed in initState; end with the inherited call), the AnimationController.dispose page (disposing twice trips a debug assertion, which supports the double-dispose warning in step 1), the ChangeNotifier.dispose page (only the owner calls it) and the TextEditingController page (dispose it when no longer needed; it does not say who owns a controller passed in). Site terms not read, facts only. The ownership rule itself (a constructor-injected controller is the caller's) and the reverse-order rule of step 2 are our reasoning from those pages, not statements of them; the dispose-runs-after-a-failed-initState trap in the guardrails is also unsourced here. 🟡: never run by us.

Independent verification 2026-10-21: 7 checked, 7 matched, 0 corrected, 0 unverified (fewer than eight checkable points in this block; all were checked).

← v1.0.0All versions