使用可能的ActivityGroup Android的内存使用问题 [英] Android Memory Usage Problem on possibly using ActivityGroup
问题描述
Android的内存使用问题
Android Memory Usage Problem on possibly using ActivityGroup
这是我结束了记忆问题搞乱有点长的故事。我开发了非常深刻的Android应用程序使用非常量的活动和框架。首先我必须说，我用ActivityGroups的主要类别，以轻松处理活动。我可以实现通过所有活动getLocalActivityManager（）。而我得到这个错误信息：
This is a little bit long story that i ended up messing with memory problems. I developed very deep android application by using very amount of Activities and Frameworks. First of all I have to say I used ActivityGroups for main categories to handle activities easily. And I can achieve all activities via getLocalActivityManager(). And I get this error message:
02-25 11:34:13.749:
ERROR/dalvikvm-heap(3042):
2764800-byte external allocation too
large for this process.
02-25 11:34:13.749:
ERROR/GraphicsJNI(3042): VM won't let
us allocate 2764800 bytes
然后我的应用程序将与各种异常崩溃，如;
then my application will crash with various exceptions, eg;
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): FATAL EXCEPTION: main
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.turkcell.seyahat/com.matriksdata.ui.schedule.MessageDetail}: android.view.InflateException: Binary XML file line #2: Error inflating class <unknown>
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2663)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.app.ActivityThread.startActivityNow(ActivityThread.java:2503)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.app.LocalActivityManager.moveToState(LocalActivityManager.java:127)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.app.LocalActivityManager.startActivity(LocalActivityManager.java:339)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at com.matriksdata.app.XActivityGroup.goForward(XActivityGroup.java:122)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at com.matriksdata.ui.parents.ScheduleActivityGroup.goForward(ScheduleActivityGroup.java:143)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at com.matriksdata.ui.schedule.MessageBox.onItemClick(MessageBox.java:81)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.widget.AdapterView.performItemClick(AdapterView.java:284)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.widget.ListView.performItemClick(ListView.java:3730)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.widget.AbsListView$PerformClick.run(AbsListView.java:1808)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.os.Handler.handleCallback(Handler.java:587)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.os.Handler.dispatchMessage(Handler.java:92)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.os.Looper.loop(Looper.java:123)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.app.ActivityThread.main(ActivityThread.java:4627)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at java.lang.reflect.Method.invokeNative(Native Method)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at java.lang.reflect.Method.invoke(Method.java:521)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:871)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:629)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at dalvik.system.NativeStart.main(Native Method)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): Caused by: android.view.InflateException: Binary XML file line #2: Error inflating class <unknown>
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.view.LayoutInflater.createView(LayoutInflater.java:513)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:563)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.view.LayoutInflater.inflate(LayoutInflater.java:385)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.view.LayoutInflater.inflate(LayoutInflater.java:320)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.view.LayoutInflater.inflate(LayoutInflater.java:276)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:210)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.app.Activity.setContentView(Activity.java:1647)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at com.matriksdata.ui.schedule.MessageDetail.onCreate(MessageDetail.java:33)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2627)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): ... 18 more
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): Caused by: java.lang.reflect.InvocationTargetException
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.widget.LinearLayout.<init>(LinearLayout.java:115)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at java.lang.reflect.Constructor.constructNative(Native Method)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at java.lang.reflect.Constructor.newInstance(Constructor.java:446)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.view.LayoutInflater.createView(LayoutInflater.java:500)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): ... 28 more
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): Caused by: java.lang.OutOfMemoryError: bitmap size exceeds VM budget
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.graphics.Bitmap.nativeCreate(Native Method)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.graphics.Bitmap.createBitmap(Bitmap.java:468)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.graphics.Bitmap.createBitmap(Bitmap.java:435)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.graphics.Bitmap.createScaledBitmap(Bitmap.java:340)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.graphics.BitmapFactory.finishDecode(BitmapFactory.java:590)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:564)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.graphics.BitmapFactory.decodeResourceStream(BitmapFactory.java:425)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:697)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.content.res.Resources.loadDrawable(Resources.java:1709)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.content.res.TypedArray.getDrawable(TypedArray.java:601)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.view.View.<init>(View.java:1885)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.view.View.<init>(View.java:1834)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): at android.view.ViewGroup.<init>(ViewGroup.java:285)
02-25 11:34:13.772: ERROR/AndroidRuntime(3042): ... 32 more
当然，我没有 2764800 字节的PNG图像，但我认为它去codeD大小。所以我想我有图像处理的问题，我检查和固定我的项目的每一个细节，以正确地处理图像。我检查了android-developers.blogspot.com/2009/01/avoiding-memory-leaks.html说明一切。我检查空可绘，我按照模型的可重用性的说明，我改变中描述的加载方式：stackoverflow.com/questions/477572/android-strange-out-of-memory-issue/823966#823966。
Of course i don’t have 2764800 byte png image, but i think its decoded size. So i thought that i had image handling problems and i checked and fixed my project in every detail to handle images correctly. I checked everything described in android-developers.blogspot.com/2009/01/avoiding-memory-leaks.html . I checked null drawables, i follow model reusability instructions, i changed loading methods described in : stackoverflow.com/questions/477572/android-strange-out-of-memory-issue/823966#823966.
此外，我很少有位图从磁盘加载。创建搭载Android XML布局文件我的所有布局。我有很多在XML文件中也描述位图。
Also i have few bitmaps to load from disk. My all layouts created by android xml layout files. I have plenty of bitmaps described in xml files also.
然后我看到，我有很大的静态类的应用程序使用内存分析仪。 i。由装载需求和使用后释放释放该静态属性。所以最后我得到了MAT此内存泄漏嫌疑人;
Then i saw that i have big static classes in application with memory analyzer. i freed that static properties by loading on demand and freeing after used. So finally i got this memory leak suspects in MAT;
的java.lang.Class，由装载3,043情况下，占领871304（17.97％）字节。
3,043 instances of "java.lang.Class", loaded by "" occupy 871,304 (17.97%) bytes.
最大的实例：
类com.ibm.icu4jni.util.Resources $ DefaultTimeZones @ 0x4014c3b0 - 166768（3.44％）字节
。
类android.text.Html $ @的HTMLParser 0x400fe448 - 126592（2.61％）字节
。
类com.google.googlenav.proto.GmmMessageTypes @ 0x4835d450 - 56944（1.17％）字节
。
类org.apache.harmony.luni.internal.net.www.protocol.http.HttpConnectionPool @ 0x47caea20 - 51872（1.07％）字节
。
类org.apache.harmony.security.fortress.Services @ 0x4008c4d0 - 51456（1.06％）字节。
Biggest instances:
class com.ibm.icu4jni.util.Resources$DefaultTimeZones @ 0x4014c3b0 - 166,768 (3.44%) bytes.
class android.text.Html$HtmlParser @ 0x400fe448 - 126,592 (2.61%) bytes.
class com.google.googlenav.proto.GmmMessageTypes @ 0x4835d450 - 56,944 (1.17%) bytes.
class org.apache.harmony.luni.internal.net.www.protocol.http.HttpConnectionPool @ 0x47caea20 - 51,872 (1.07%) bytes.
class org.apache.harmony.security.fortress.Services @ 0x4008c4d0 - 51,456 (1.06%) bytes.
java.lang.String中，由系统类加载器'装载8,721实例占用549624（11.33％）个字节。 Keywordsjava.lang.String
8,721 instances of 'java.lang.String', loaded by 'system class loader' occupy 549,624 (11.33%) bytes. Keywords java.lang.String
org.bouncycastle.jce.provider.X509CertificateObject，由系统类加载器装60的实例占用300024（10.76％）个字节。这些实例是从的java.util.Hashtable $ HashtableEntry []一个实例引用，以系统类加载器Keywordsorg.bouncycastle.jce.provider.X509CertificateObjectjava.util.Hashtable $ HashtableEntry []
60 instances of "org.bouncycastle.jce.provider.X509CertificateObject", loaded by "system class loader" occupy 300,024 (10.76%) bytes. These instances are referenced from one instance of "java.util.Hashtable$HashtableEntry[]", loaded by "system class loader" Keywords org.bouncycastle.jce.provider.X509CertificateObject java.util.Hashtable$HashtableEntry[]
这第三个没有发生每次。通常，当我使用的内存管理器中的GalaxyTab。
This third one not occurs every time. Generally when i use memory manager in GalaxyTab.
我最大的顶级霸主类是这些。的http://www.matriks.mobi/arge/android/Screen%20shot%202011-02-25%20at%2012.19.08%20PM.png
My biggest Top-level Dominator Classes are these. http://www.matriks.mobi/arge/android/Screen%20shot%202011-02-25%20at%2012.19.08%20PM.png
我刚刚2或3活动，生活和他们的休息暂停。我得到这个消息的组件报告。当然，这并不是说我只用1.5 MB RAM的解释，因为根据内存管理器我的应用程序使用48 MB内存高达约20 MB。
I have just 2 or 3 activities live and the rest of them are suspended. I get this messages in components report. Of course this is not the explanation that i use just 1.5 MB of ram, because according to memory manager my application uses 48 MB of ram up from about 20 MB.
可能浪费内存 * 重复的字符串的* 发现0出现的char []与具有相同的内容至少有10个实例。总的大小为0字节。
Possible Memory Waste * Duplicate Strings* Found 0 occurrences of char[] with at least 10 instances having identical content. Total size is 0 bytes.
我觉得那不是我想要:)的东西位于 HTTP ：//www.matriks.mobi/arge/android/android5706014442078310727.hprof.zip
i think thats not the thing that i want :) hprof file located in http://www.matriks.mobi/arge/android/android5706014442078310727.hprof.zip
我猜测，我有问题的ActivityGroup类。至少我保持在栈LocalActivityManager活动和活动标识。但是，即使我不创造新的活动，并加载那些之间传递，内存增加。
I am guessing that i have problem with ActivityGroup class. At least i am keeping activities and activity ids in LocalActivityManager in stacks. But even if i don’t create new activities, and passing between loaded ones, memory increases.
我知道这是不是寻找泄漏的方式，可能我有一个code基础问题导致此内存泄漏。但是，我应该检查任何一个想法会非常非常欢迎在这里，因为我有点坚持在这里。
I know this is not the way of searching for leaks, and possibly i have a code based problem causing this memory leaks. But any single idea that i should check will be very very welcome here, because i am kinda stuck here.
推荐答案
尝试的追踪内存分配的，而应用程序正在使用中。
Try tracking memory allocations while application is in use.
此外，持有到位图可绘制可以产生内存泄漏。当绘制对象添加到查看，循环引用被创建。所以，当你持有一个引用位图绘制，它还拥有一个引用视图这种观点永远不能GCed。
Also, holding references to Bitmap Drawables can produce memory leaks. When a Drawable is added to View, a circular reference is created. So when you hold a reference to Bitmap drawable, it further holds a reference to a View and this View can never be GCed.
要避免它的最简单的方法就是提取一个位图绘制对象的位图和保持对它的引用，那么当活动重新启动/重新加载，你从这个位图创建新的位图可绘制。这是怎样一个照片流示例工作（在末尾描述）： 更快的屏幕方向变化
The easiest way to avoid it is to extract a bitmap from a Bitmap Drawable and hold a reference to it, then when Activity is restarted/reloaded, you create new Bitmap Drawables from this bitmaps. This is how a Photostream example works (described at the end): Faster screen orientation change
这篇关于使用可能的ActivityGroup Android的内存使用问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
