Fixed
Status Update
Comments
me...@gmail.com <me...@gmail.com> #3
[Comment deleted]
me...@gmail.com <me...@gmail.com> #4
[Comment deleted]
me...@gmail.com <me...@gmail.com> #6
Happens every time I return to homescreen on Nexus 5.
il...@google.com <il...@google.com>
mi...@gmail.com <mi...@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
lb...@gmail.com <lb...@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.
ab...@gmail.com <ab...@gmail.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.
me...@gmail.com <me...@gmail.com> #10
the same things.... after some time the ram gets filled up! nexus7 2nd
ab...@gmail.com <ab...@gmail.com> #11
LRX21P Nexus 7 2013 (32gb, encrypted), same issue. Background processes restarting en mass, performance goes down the toilet, device memory listed as critical in procstats with usually circa 800-1200MB system memory in use.
lb...@gmail.com <lb...@gmail.com> #12
I'm also experiencing this issue!
jb...@google.com <jb...@google.com>
sa...@google.com <sa...@google.com>
ap...@google.com <ap...@google.com> #13
Here is my meminfo dump. I can't see any particular reason from meminfo dump but it occurs when I use Spotify or Pocket Casts.
sa...@google.com <sa...@google.com>
lb...@gmail.com <lb...@gmail.com> #14
#5, #8, #9, #10, #11: Your comments do not add anything to what is already known about this issue. They only flood the inboxes of people subscribed to this bug. If you experience the bug, star it. This is enough to make developers aware of how many people are affected. Please post comments only if you have anything significant to share.
jb...@google.com <jb...@google.com> #15
Same deal here. Launcher redraws almost every time I go back to my home screen. Overall lollipop is very laggy on my Nexus 5. Have tried wiping cache via recovery with no effect.
lb...@gmail.com <lb...@gmail.com> #16
Same here after a day multitasking is impossible and constant launcher redraws.Come on Google launcher redraws in android 5.0 on 2gb of ram!
na...@google.com <na...@google.com> #17
same here after rebooting the system usage is 360 mb and free ram is 1.3 gb, but after a days usage the system ram consumption is 1 gb n free ram is 400 mb which is making my nexus 5 lag and making multitasking nearly impossible. Please resolve this issue google dont want to reboot my nexus 5 every alternate day.
lb...@gmail.com <lb...@gmail.com> #18
Nexus 5, using over 1 Gb after 2 days.
lb...@gmail.com <lb...@gmail.com> #19
[Comment deleted]
pr...@google.com <pr...@google.com> #20
On Moto G 2nd gen with 5.0, Navigation and Play Music are completely unusable. These and other apps randomly close as if RAM is exhausted, despite system reporting plenty. While driving with screen off, Navigation will silently close. I hafta continuously check my phone to make sure it's still actually navigating! Play Music closes, again with screen off and nothing else going on. What background process could possibly be so important that it stops my music and/or navigation? How does 300+MB of "free" RAM suddenly get exhausted when I'm not actively using my phone? Launcher almost always needs to redraw. Chrome always redraws open tabs, even after switching to Launcher and back. My phone is essentially thrashing continuously, and can't even run ONE app at a time reliably.
Was considering replacing my brand new phone with one with more RAM -- glad to see other people having the same problem. Definitely an OS problem!
Was considering replacing my brand new phone with one with more RAM -- glad to see other people having the same problem. Definitely an OS problem!
lb...@gmail.com <lb...@gmail.com> #21
Same here, i have to keep rebooting my nexus 5, i like android lollipop but, it uses ram too much...
th...@gmail.com <th...@gmail.com> #22
I have been logging the memory info from "top" output and /mem/procinfo during a few days. After like 2 days, it started killing the launcher, but would be good for a day again if I "swiped out" all apps from the task switcher.
Looking at the numbers, I can't find a reason for this behavior, to be honest. memory usage is pending, but I always have 600-700 MB reported as free, which shouldn't be the cause for starting killing apps (or restarting them), of course, on a newly booted phone I have 1.1-1.2 GB available, which is plenty.
After about 5 days, the phone started to kill the launcher no matter what I did, so i dumped output before, and after a reboot. I didn't see anything obvious between them. I've attached them if anyone wanna study the output.
One theory could be that the free memory calculation (that controls application killing) is broken.
Looking at the numbers, I can't find a reason for this behavior, to be honest. memory usage is pending, but I always have 600-700 MB reported as free, which shouldn't be the cause for starting killing apps (or restarting them), of course, on a newly booted phone I have 1.1-1.2 GB available, which is plenty.
After about 5 days, the phone started to kill the launcher no matter what I did, so i dumped output before, and after a reboot. I didn't see anything obvious between them. I've attached them if anyone wanna study the output.
One theory could be that the free memory calculation (that controls application killing) is broken.
lb...@gmail.com <lb...@gmail.com> #23
Everytime i get the first battery low notification, i also get a popup saying Google Play Music has stopped working!
Description
Version used: 1.5.2
Devices/Android versions reproduced on: Android 12
I'm using SearchView in my Activity. If SearchView is expanded and i'm opening DialogFragment on the top of the activity and then dismissing it, SearchView is being collapsed. It must not collapse.
Seems like some bug in Fragment 1.5.0 - 1.5.2 version. In 1.4.1 version everything is working fine.
Please suggest some workarounds or how to fix this issue?