Fixed
Status Update
Comments
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #3
[Comment deleted]
ap...@google.com <ap...@google.com> #4
[Comment deleted]
il...@google.com <il...@google.com> #6
Happens every time I return to homescreen on Nexus 5.
e....@gmail.com <e....@gmail.com> #7
This is a real problem. As the hours pass system ram consumed gets bigger and bigger. It gets to the point that I have to reboot my device because apps keep reloading and sometimes even the launcher has to reload.It is a serious issue. I have to reboot daily
e....@gmail.com <e....@gmail.com> #8
When play music crashed in the background today, with maps navigation running in the forefront, system ram usage was at 780mb. Maps ram usage was at 280mb. The play music process was stuck in "restarting" status until I swiped it out of recents and restarted it. This was after around 48 hours uptime. Camera app also started crashing mid-photosphere shortly after this. After a reboot system usage dropped to ~380mb and everything's working fine again.
il...@google.com <il...@google.com> #9
Have the same issue here, after around 40 hours of on time home gets redrawn every time I return to it, and when I go to Settings>Apps>Running, most of the running apps are restarting. A reboot fixes the issue.
sl...@gmail.com <sl...@gmail.com> #10
the same things.... after some time the ram gets filled up! nexus7 2nd
Description
Component used: Activity Version used: 1.2.0-alpha06
The APIs of
LifecycleOwner
provide us with a callback for when you reach theCREATED
state, but for activities that is often after some critical code needs to run.For example:
setTheme
to reset your theme from a branded launch themesetLocalNightMode()
These all need to be called before
super.onCreate()
and specifically the inflation of any layout.It would be nice if there was a composable way to get a callback at that exact time without needing to manually add code to
onCreate()
(which, will fine for app code, is hard to do as a library).