Serious memory leak - last update

After updating to the latest version (2.0.4304) and rebooting the phone, the RAM usage shows about 140MB more than prior the update (currently 715MB of used RAM in total). To confirm, I have reverted to the previous version (2.0.3917) and rebooted (twice): the RAM usage upon EACH complete reboot went back to about 570MB of used RAM.
On the other hand, under running programs, Android shows Avast having 1 process and 3 services upon reboot, totally taking 12MB of RAM. The HUGE contradiction (12MB vs. 140MB) is where I suppose the memory leak is happening.

Please respond a.s.a.p.

EDITED:
NOTE: All MB values represent the used RAM (immediately) after a reboot is completed.

1. Updated Avast from 2.0.3917 to 2.0.4304 through Google Play and rebooted (715MB used RAM)

2. Reverted to the old version using TB and rebooted (570MB used RAM)
3. Cleared cache and Dalvik cache and rebooted.
4. Re-installed the new version using TB and rebooted (715MB used RAM)

5. Avast completely removed (including Anti-Theft) and rebooted (560MB used RAM)
6. Clean re-installed Avast 2.0.4304 from Google Play (including Anti-Theft - root installation), configured it and rebooted (715MB used RAM)
7. Uninstalled ONLY Avast (left Anti-Theft - root installation) and rebooted (570MB of used RAM)

Unequivocal, I guess!!

EDITED:
SOLVED!!! SEE BELLOW!

Well I have the latest version, and in my android 4.2.2 Settings L APPS > Running it shows avast as having 1 process and 8 services for 27MB of a total for running apps of 442MB. I only have 9 apps running.

Depending on what you are doing avast may use more RAM if scanning, etc.

My scenarios were clearly described as:

  1. right after reboot - old version (570MB of used RAM)
  2. right after reboot - new version (715MB of used RAM)

I think this leaves room to no interpretations whether Avast is was scanning or other variables were involved! Furthermore I have Avast set so it would NOT perform any automatic scanning (under “scanning” section).

Well I rarely reboot, but I can only go with the figures I have got after the update and it is using 27MB.

…and you’re checking that usage where? (most likely under Running)

Yes as I said under the running apps.

Well, if you’re going by that, it’s absolutely irrelevant. How about making a comparison how much memory (available RAM) are you having NOW and how much were you having BEFORE installing the last version. That’s why I have rebooted several time to eliminate variables (like other programs caching, or running in background, services loading, queried intents, etc)

Check your available RAM! NOT the reported running value - that’s exactly the point I’m trying to make (anyway, without knowing the previous value it’s pointless)

Any Avast member, please?

The problem is I have never had a match where available ram plus ram used has ever equalled the installed 1GB ram. So I can’t say where this discrepancy lies.

Hopefully one of the avast mobile guys can get to this topic, but given the time zone Central European Time that may be tomorrow.

Yeah, hopefully! Anyway, check the first thread, I’ve done some additional tests and updated the post.

Hi,

try to turn off the File Shield and see if that makes any difference.

Filip

YES!!! Turning OFF the File Shield brought back the RAM usage to (570-580)MB
Thank you! :slight_smile: Good reason to uninstall Cerberus. :wink:

No problem, but if I might suggest, you should look into your SD card(s). We made some experiments today on a common user SD cards and the differences with and without File Shield were around 6-7MB. Something is really wrong with yours if it’s 130MB or so (maybe some app doing some weird business there without your knowledge).

Filip

What exactly should I be looking for considering your comment “maybe some app doing some weird business there without your knowledge”? Only internal or external SD too?

Well depends on what you have, I’m talking about what Android OS considers to be the SD card/storage on your device.

I would look for a lot of folders (empty or filled with small files) and by lot of I’m talking about thousands or more probably. Or it can be constant activity on your SD card, which can be directories being created and deleted very, very often, files being written etc.

Filip

Hm…constant activity, no, I don’t think so: I’m closely monitoring phone’s activity using Better Battery Stats and I don’t have any weird wake-lock or other weird activity; furthermore the battery life is, actually quite good at about 0.7-1.0 %/hour with the screen off BUT I have recently installed Real Race 3, it’s mainly installed under /sdcard/Android/data/com.ea.games.r3 and there are 922 folders containing 6402 files, for a total of 1.14GB. Although most likely there is no activity (as in read/write) when the game is off, the number of files and their size might actually be the answer for this “hiccup”. However, if that’s the case, I’m most likely falling under the “typical users” category, I guess - which means you should worry about that new feature. After all the game itself is free, you might as well install it, just for the hack of it and see what happens. See whether the tested 6-7 MB turns into 130-140 MB. That might give you a very good insight on what to do next.

Anyway, Filip, thanks a lot for your kind support.

I think some people have it installed here and nobody complained about memory consumption. I’ll see if I can find time to test it by myself today.

Filip

Hi,

I’ve done some tests myself and it seems the discussed issue may be caused by:

  • large games installing thousands of files/folders “forever” changing and
  • some/most social network apps (i.e. Facebook is notorious for storing large cache of files having some names incompatible with many storage media - that in turn might cause Android mediaserver or the scanner to run extensively)

Well, I’m experiencing crashes and even reboots with avast! File Shield ON and Rom Toolbox Pro backuping apps+data.
I’m blaming Rom Toolbox, or, better, I’m trying to solve with their support.
Could it be avast! fault?

Hi guys,

can you both try disabling read scanning if you have it on? It should be better with write scanning only. If not, let me know.

Filip

Mine is already on scan only on writing.
Can you check an aLogcat I’ve generated while using avast! + Rom Toolbox and the phone is crashing? I’ll also send my phone specs.
I know it’s not your business, but, maybe you can help me…