top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration
Print Preview

emulator memory leak when GPU on using android.

+2 votes
106 views

I find that the emulator's memory increase rapidly when check GPU on. You can do the reproduction as following:
1. Turn on GPU following http://developer.android.com/tools/devices/emulator.html#acceleration
2. Power on the emulator
3. Launch some apps by mouse, (i,e. launch Settings then Clock, and Settings then Clock ...)
4. Check the memory usage of emulator by top command on Ubuntu and ProcessExplorer on Windows

I found that the apps with property android:hardwareAccelerated="true" is more worse.

posted Sep 4, 2013 by Jagan Mishra

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button

Similar Questions
+1 vote

I found that most released apps(including system apps) can be debugged on the emulator by the way following:
1. install the app on the emulator, and launch it
2. run adb shell ps to get the pid of the app
3. run adb jdwp, if you find the pid in the output, then you can attach to the app by running
adb forward tcp:1234 jdwp:$pid_you_find and jdb -connect com.sun.jdi.SocketAttach:hostname=localhost,port=1234
4. you can use commands such as "classes" to see the classes of the app, even "stop" to set breakpoint and "eval" to run many functions and see the members of the objects.
I have 2 questions:
1. Why these tricks fail on the phones? What's the difference between the rom of emulator and phones?
2. How to avoid my app being debugged through such way?

+1 vote

I have installed my custom app in Packages/apps/

in the app, I use a simple Videoview for video playbacks (3gp or mp4). it works in actual device/ADT emulator, but If I run it in AOSP emulator, it says "Failed to open file : the path of the video"

// Retrieving file from internal file 
systemVideo.setVideoURI(Uri.parse("android.resource://" + getPackageName() + "/" + R.drawable.test));
+2 votes

I wishito know if android's Garbage Collection mechanism affects memory held in the native side ( especially the memory held by android.graphics.Canvas objects ).
Occassionally, I see crashes in libskia.so immediately following a GC operation on the same process that crashed. I 'm unaware of the VM's GC operation but am interested to know how native memory is affected by GC.


Useful Links with Similar Problem
Contact Us
+91 9880187415
sales@queryhome.net
support@queryhome.net
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Bangalore-560102
Karnataka INDIA.
QUERY HOME
...