1
我有这个问题Android: Screen orientation error + VM won't let us allocate x bytes 所以我决定下载Eclipse Memory Analyzer。当我的错误出现时我运行它,我有3个疑问嫌疑人,但我不明白它可能来自哪里。 +我真的不知道,如果我的问题是由于内存泄漏的可能的泄漏仅取2.2,B空间 Android:使用Eclipse内存分析器检测泄漏
问题可疑1
2,094 instances of "java.lang.Class", loaded by "<system class loader>" occupy 789,200 (33.76%) bytes.
Biggest instances:
•class android.text.Html$HtmlParser @ 0x4018d3f0 - 126,632 (5.42%) bytes.
•class org.apache.harmony.security.fortress.Services @ 0x400e2e58 - 53,880 (2.30%) bytes.
•class com.android.internal.R$styleable @ 0x400882c0 - 38,072 (1.63%) bytes.
•class libcore.icu.TimeZones$CachedTimeZones @ 0x40444fa8 - 37,712 (1.61%) bytes.
•class android.R$styleable @ 0x40055940 - 37,640 (1.61%) bytes.
•class android.content.res.Resources @ 0x40075178 - 36,032 (1.54%) bytes.
•class android.text.AutoText @ 0x40178980 - 31,656 (1.35%) bytes.
Keywords
java.lang.Class
问题可疑2
128 instances of "org.bouncycastle.jce.provider.X509CertificateObject", loaded by "<system class loader>" occupy 455,112 (19.47%) 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[]
问题SUSPECT 3
6,822 instances of "java.lang.String", loaded by "<system class loader>" occupy 418,104 (17.89%) bytes.
Keywords
java.lang.String
你认为我有泄漏吗?我们可以从我发布的内容中说出来吗? 谢谢