IssueTracker

Hi Google, this is very important for a company that makes product like we do http://carbyne911.com/

We deliver a life saving platform for 911 centers around the world, making it easier to emergency services for all kinds to get faster to citizens, including indoor and outdoor location and we're relaying in some case on the admin area to help us direct the forces

Please consider adding it to Singapore and other missing countries

Thanks for your suggestion!
We have passed the suggestion on to the product team for further consideration.
Please star to add your vote and receive further updates, and feel free to add any comments to discuss your use case.

*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************

I've transitioned from this team. Thanks!

I'm going to add a few more reports then I'm going to try factory resetting again as this is very frustrating and annoying, may even downgrade to KitKat as it was smother and faster for me.

I found same report: https://code.google.com/p/android/issues/detail?id=79729

Bug report I'll do little later (i'am rebooted my nexus).

Would like to share a bug report too, but it warns me not to share with public? Is there an Android issues email?

Same problem! I should reboot my phone everyday because of that. System use most of ram after one day of use!!

Same problem. 70 hours uptime and less than 500Mb free.

1-st bug report.

2-nd bug report (Launcher redraws when return to homescreen)

ZIP because "Max. attachments per comment: 10.0 MB"

Same problem on my Nexus 5. Less than 400 Mb free after one day of work. Have to reboot every day.

3-rd report.

Thanks for the bug reports. We may need more information -- we will let you know.

I'll wait.

I could. Awesome screenshot.

Last bug report:

Ditto the above situation, but on a 2013 Nexus 7- device memory critical, high system RAM use, background services restart en mass. When it happens again I'll catch a bug report.

The same problem. Put clean through fastbut system. after 10 days the problems started with the RAM.

Same issue here. I've to reboot the phone almost everyday for it to function normally. When the phone is running smoothly, 'system'uses 300-400 MB RAM tops. But when the device starts to lag, apps begin to restart frequently on their own. At this point in time, 'system' uses more than 700 MB RAM. Rebooting solves it temporarily.

[Comment deleted]

#8, #10, #14, #22, #23, #24: 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.

I've noticed that when the "System" RAM peaks (800MB+) and the launcher constantly restarts, there is nothing listed under "Show cached processes". Is is possible that for some reason the OS has stopped caching processes, meaning they have to restarted whenever they need to be used? Hope this is useful!

[Comment deleted]

I can relate to this.

Memory management on lollipop is not ready for prime time.

Launcher gets killed too easily, and that's really annoying.

Is bug report useful? Memory usage of system is increased overtime, like, hours or days.

Keeping WiFi off helps me. Then reboot the phone once to clear the leak. May someone else try it.

I tried that (with Wi-Fi always scan option disabled as well) a few days ago.
After one day with LTE, it still happened, don't know why.

I see. I don't have LTE.

I was using clean master- a task killer app... However after doing some research I found people not recommending to use such apps.  Hence removed it from my nexus 5 and now the phone runs smoothly as ever.  Facing no performance issues from last 3 days and doesn't even need to restart as well..

Even after clearing recent on my nexus 5, phone so laggy.. I have to restart to bring normal every time.

Only rebooting fixes it.

BTW, this has been fixed. Will roll out in the next update.

Even i am facing this memory leak problem. Never happened with kitkat 4.4. After lollipop 5.0.1 this phone really sucks. After a day or two the system is taking 1.2 gb ram and restarting all other apps. The phone starts hanging like anything. Really frustrated after updating to lollipop. Why does google not fixing it. Either fix it or give an easy link to downgrade to kitkat 4.4.4

screenshots attached

Google'll fixed it... on March.

Been using 5.1 for a few days now and so far so good. System RAM consumption stays around 330MB - 400MB. Finally, lollipop goodness!

On my Nexus 5 with Android 5.1 it has not been fixed. Now after 191h uptime System memory usage is 1.4Gb.

Is it perhaps surfaceflinger or mdss_fb0 (part of MSM8974 chipset drivers) that leaks?

shell@hammerhead:/sys/kernel/debug/ion $ cat iommu
cat iommu
          client              pid             size
----------------------------------------------------
----------------------------------------------------
orphaned allocations (info is from last known client):
        mdss_fb0              346          5505024 0 1
        mdss_fb0              346          5505024 0 1
        mdss_fb0              346           442368 0 1
        mdss_fb0              346          8847360 0 1
        mdss_fb0              346          8847360 0 1
        mdss_fb0              346          8847360 0 1
  surfaceflinger              176          8847360 0 1
        mdss_fb0              346          8847360 0 1
        mdss_fb0              346          8847360 0 1
        mdss_fb0              346         10321920 0 1
  surfaceflinger              176          8847360 0 1
        mdss_fb0              346          5505024 0 1
  surfaceflinger              176          8847360 0 1
  surfaceflinger              176         14221312 0 1
        mdss_fb0              346          5505024 0 1
        mdss_fb0              346          5505024 0 1
        mdss_fb0              346          8847360 0 1
        mdss_fb0              346          8847360 0 1
        mdss_fb0              346          8847360 0 1
----------------------------------------------------
  total orphaned        149831680
          total         149831680
----------------------------------------------------


adb shell dumpsys meminfo
Total PSS by category:
   210180 kB: Dalvik
   173483 kB: Native
    79616 kB: EGL mtrack
    33672 kB: GL mtrack
    29769 kB: .dex mmap
    22213 kB: .so mmap
    21301 kB: .art mmap
    15192 kB: Gfx dev
    15187 kB: .oat mmap
    14516 kB: .apk mmap
    11888 kB: Dalvik Other
    10094 kB: Unknown
     6784 kB: Stack
     2485 kB: Other mmap
      334 kB: .ttf mmap
      171 kB: Other dev
       40 kB: Ashmem
        4 kB: Cursor
        4 kB: .jar mmap
        0 kB: Other mtrack

Total RAM: 1900556 kB (status low)
 Free RAM: 236802 kB (54478 cached pss + 116732 cached kernel + 65592 free)
 Used RAM: 797007 kB (592455 used pss + 204552 kernel)
 Lost RAM: 866747 kB
   Tuning: 192 (large 512), oom 184320 kB, restore limit 61440 kB (high-end-gfx)

Please check the issue on android latest build on nexus 5 and let us know the result.

Dnaga,

The issue persists on M4B30X.

Please share bugreport for M4B30X build.

Android bug report:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.

Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.

We are closing this issue as we don't have enough actionable information. If you are still facing this problem, please open new issue and add the relevant information along with reference to earlier issue.