Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Android Studio Build: 2024.2.1
Kotlin version: 2.0.21
From debugging, the composition disposes itself when leaving the fragment due to the lifecycle listener in WrappedComposition, but this doesn't null out the `composition` field within ComposeView, leaving a ComposeView in the view pool with a dead composition, that neither renders anything nor throws an error when calling setContent(). Would expect it to either call disposeComposition() at the ComposeView level so that the next call to setContent() creates a new composition, or not dispose at all since the view hasn't been removed from the view pool.