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)
Attachment actions
Unintended behavior
View staffing
Description
Version used: 1.8.0-SNAPSHOT
I've written a test to showcase a bug I encounter in real world usage where sometimes when navigating back using the 'navigate up' back button, the animation is not played and the top fragment remains on top. It seems to happen in combination with a shared element transition and predictive back.
Navigating back from this undefined state triggers a memory leak.
The test is available in the sample project: