[Bug]: Compose-related memory leaks

[brian-livefront]

Is there an existing issue for this?

• I have searched the existing issues

Is there a StackOverflow question about this issue?

• I have searched StackOverflow

What happened?

The SearchViewModel (and likely other ViewModels) appears to leak after navigating to the search screen and back to the main screen. This seems to be related to this Compose issue.

Steps to reproduce

• Open the app.
• Navigate to the search screen.
• Enter text in the search field.
• Exit the search screen.
• Open the memory profiler, attempt to force a garbage collection several times, and then collect a heap dump.
• Search for SearchViewModel in the heap.

The SearchViewModel will still be present in the heap even though the screen was left and many garbage collections were attempted.

Relevant logcat output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct