2011-01-07 50 views
0
[ 01-01 08:29:02.954 1511:0x5e7 E/dalvikvm ] 
HeapWorker is wedged: 10330ms spent inside Landroid/content/ContentResolver$CursorWrapperInner;.finalize()V 
[ 01-01 08:29:02.954 1511:0x5e7 I/dalvikvm ] 
DALVIK THREADS:  
[ 01-01 08:29:02.954 1511:0x5e7 I/dalvikvm ] 
"main" prio=5 tid=1 RUNNABLE  
[ 01-01 08:29:02.954 1511:0x5e7 I/dalvikvm ] 
    | group="main" sCount=0 dsCount=0 s=N obj=0x400258c8 self=0xcd98 
[ 01-01 08:29:02.954 1511:0x5e7 I/dalvikvm ] 
    | sysTid=1511 nice=0 sched=0/0 cgrp=default handle=-1345021912 
[ 01-01 08:29:02.977 1511:0x5e7 I/dalvikvm ] 
    at java.lang.AbstractStringBuilder.toString(AbstractStringBuilder.java:Note: 0000662) 
[ 01-01 08:29:02.977 1511:0x5e7 I/dalvikvm ] 
    at java.lang.StringBuilder.toString(StringBuilder.java:664) 
[ 01-01 08:29:02.977 1511:0x5e7 I/dalvikvm ] 
    at java.io.File.join(File.java:264) 
[ 01-01 08:29:02.977 1511:0x5e7 I/dalvikvm ] 
    at java.io.File.<init>(File.java:175) 
[ 01-01 08:29:02.977 1511:0x5e7 I/dalvikvm ] 
    at java.io.File.<init>(File.java:142) 
[ 01-01 08:29:02.977 1511:0x5e7 I/dalvikvm ] 
    at java.io.File.filenamesToFiles(File.java:1082) 
[ 01-01 08:29:02.977 1511:0x5e7 I/dalvikvm ] 
    at java.io.File.listFiles(File.java:1008) 

如何解决此问题?HeapWorker Android性能

我知道根本原因是要创建很多临时变量。

回答

3

您正在查看错误线程的堆栈跟踪。

问题是终结器需要超过10秒才能完成,因此VM认为它已死锁并中止导致应用程序重新启动。在这种情况下,停顿的函数是android.content.ContentResolver.CursorWrapperInner.finalize()。

附近应该有HeapWorker线程的堆栈跟踪。

+0

`HeapWorker楔入:在Landroid/database/sqlite/SQLiteCompiledSql中花费33299ms; .finalize()V`嵌套的sqlite事务会导致这种情况发生吗? – 2015-02-05 22:03:33