Feature Request P3
Status Update
Comments
ma...@google.com <ma...@google.com> #2
Hello, can you please attach a sample that reproduces your error?
ub...@gmail.com <ub...@gmail.com> #3
I’ve attached two screen recordings demonstrating the mediator's behavior during the first and second launches after installation. Additionally,
Description
Description:
It would be generally useful to know in Compose code when the system invokes ComponentCallbacks.onLowMemory() or ComponentCallbacks2.onTrimMemory(), to take steps to reduce memory usage. As these signals are standard Android framework mechanisms, there should be a ready-made way to observe them from Compose.
Use Case:
I'd like to propagate ComponentCallbacks.onLowMemory() to a MapView deeply embedded in the Compose tree, as recommended by MapView documentation. GoogleMap eats a lot of memory, so this seems an important detail.