To better understand/how to analyse memory usage, you probably want to
check:
http://android-developers.blogspot.com/2011/03/memory-analysis-for-android.html
http://ttlnews.blogspot.com/2010/01/attacking-memory-problems-on-android.html
http://stackoverflow.com/questions/2298208/how-to-discover-memory-usage-of-my-application-in-android/


On 9 sep, 06:43, hooked82 <djdav...@gmail.com> wrote:
> I'm checking my app for Memory Leaks/Usage and came across something
> weird that I've only seen so far in Android 1.6 and 2.1. After
> clicking around in the app a bit and I run "adb shell dumpsys meminfo"
> for my application, I see the following:
>
> DUMP OF SERVICE meminfo:
> Applications Memory Usage (kB):
> Uptime: 34639912 Realtime: 153524709
>
> ** MEMINFO in pid 5778 [com.app.myapp] **
>                         native    dalvik     other   total
>             size:    14336     4679      N/A    19015
>        allocated:  13971     4139      N/A    18110
>             free:        280       540      N/A       820
>            (Pss):     2986     4181    13491    20658
>   (shared dirty):    972     3948      620       5540
>     (priv dirty):     2876     3224    10976    17076
>
>  Objects
>                  Views:      545          ViewRoots:        4
>        AppContexts:       32             Activities:       31
>                 Assets:        2    AssetManagers:        2
>        Local Binders:       43     Proxy Binders:       79
>   Death Recipients:        2
> OpenSSL Sockets:        1
>
>  SQL
>                 heap:       91               dbFiles:        0
>        numPagers:        4   inactivePageKB:        0
>     activePageKB:        0
>
>  Asset Allocations
>     zip:/data/app/com.app.myapp.apk:/resources.arsc: 119K
>
> The memory dump was after clicking around in the app, going from
> Activity to Activity and that is all.  This isn't reproduce-able in
> 2.2+ and it seems that I'm either missing something simple, or there's
> something about pre 2.2 versions of Android that I'm just not aware
> of.  What could be the cause of this?
>
> The app will eventually crash with an OutOfMemoryError once the
> objects pile up.  Thanks!

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to