Hi! I'm using androidx.navigation:navigation-compo...
# compose
f
Hi! I'm using androidx.navigationnavigation compose2.4.0-beta02. Every time I make a NavController.navigate call, I see graphic memory allocations of roughly 30Mb to 100Mb that never get reclaimed by the GC. This leads to Out of memory errors within 5mn of normal use of my app. Am I doing something wrong? If the solution is not clear, what can I do to investigate the issue?
i
There's profiler tools built into Studio and tools like LeakCanary if you want to check for leaks in your own code: https://square.github.io/leakcanary
­čÖĆ 1
f
Thank you, I did not know about LeakCanary.