Have you seen leaks caused by navigation stacks that just kept growing over time?

A memory leak caused by navigation stacks that kept growing over time is described. The root cause was storing view models outside the navigation stack, meaning they were never deallocated when views were popped. The fix involved enforcing strict ownership rules where the stack exclusively owns its state, ensuring objects are released when removed from the stack.