I know there's a special thread to discuss the findings, I tried to sift through it, but I found something just now that truly amazed me.
App memory for every OS so far (for me) has just ticked away... never recovers. With this OS I have been closely monitoring it because I thought this was happening.. What is it?
IT IS RECOVERING... I mean, the app memory will get used, then when it's done being used, it goes back. I don't think this has happened yet to me at all, but I like it! I may never need to reset it if this is the case.
It has recovered over 6mb once and 2-3 MB more than once.
Hmm guess my storm is the only one with a memory hogging .141 O.S, cause my memory is going lower than a go go dancer..
Keep in mind, a new OS build MAY introduce new memory leaks in 3rd party apps. Though it is a pain in the arse, it's beneficial to nuke the berry and start with a clean install of the OS (no 3rd party apps). Start adding apps one by one, allowing some time between each install; until you start noticing a leak problem. At that point, delete that app and check for an update for it, if no updates are available, don't use it on the build you're running. Continue this process until all memory-friendly apps are reinstalled, and apps with leakage problems are updated and tested again, or not used at all.
My PBA Bowling app never had a leakage problem on earlier builds, but on .141 it made my free app memory plunge from 36.7MB to 9.4MB in 15 minutes with the Berry idle (starting from a fresh physical battery pull) - App deleted, memory goes down perhaps 0.5MB in the same 15 minutes, and remains above 30 for the most part.
Keep in mind, a new OS build MAY introduce new memory leaks in 3rd party apps. Though it is a pain in the arse, it's beneficial to nuke the berry and start with a clean install of the OS (no 3rd party apps). Start adding apps one by one, allowing some time between each install; until you start noticing a leak problem. At that point, delete that app and check for an update for it, if no updates are available, don't use it on the build you're running. Continue this process until all memory-friendly apps are reinstalled, and apps with leakage problems are updated and tested again, or not used at all.
My PBA Bowling app never had a leakage problem on earlier builds, but on .141 it made my free app memory plunge from 36.7MB to 9.4MB in 15 minutes with the Berry idle (starting from a fresh physical battery pull) - App deleted, memory goes down perhaps 0.5MB in the same 15 minutes, and remains above 30 for the most part.
Yeah, unfortunately, this is the exact process I have taken with both 132 and 141. In each build, I leak up to 20 mb (max, normal is around 10-15) without any 3rd party apps/themes installed.
