On 06/06/14 10:31, Alan Pope wrote: > On Fri, Jun 6, 2014 at 10:21 AM, Oliver Grawert <o...@ubuntu.com> wrote: >> hi, >> Am Mittwoch, den 04.06.2014, 18:37 +0100 schrieb Alan Pope: >> >>> Most recently last night my phone was unusable after being sat on my >>> desk for a few hours with some applications running. >> >> FTR there is also https://bugs.launchpad.net/bugs/1325580 while not >> actively leaking it surely contributes to limiting the app lifecycle (or >> rather the amount of apps you can run before one gets SIGKILLed in the >> background) >> > > And another for the list.. > > https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1304362 > > Last night I left my mako running #69 with no apps open, on charge and > by the morning the location service had risen to be the #1 memory > user. > > From this at 1AM > 14.3 MiB + 491.0 KiB = 14.7 MiB ubuntu-location-serviced > > To this at 10AM > 161.1 MiB + 580.5 KiB = 161.7 MiB ubuntu-location-serviced > > I'm thinking we should be tagging and tracking these memory leakers, > do we already have a tag for tracking them? > > Cheers, > FYI, smemstat version 0.01.10 now has the -p option allowing one to track memory changes on one or more specific processes, so that may help. Also health-check can track heap and mmap usage, so it can give some context to why applications are growing in size over time.
Colin -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp