您的位置:首页 > 产品设计 > UI/UE

最近在用parse的时候遇到的BUG.A resource was acquired at attached stack trace but never released.

2014-07-21 20:34 309 查看
这个问题怎么因为是使用第三方的包.所以没办法详细追究代码里面的问题.就先贴出来.后面再看下解决方案吧.

07-21 19:33:53.145: E/StrictMode(21289): A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.

07-21 19:33:53.145: E/StrictMode(21289): java.lang.Throwable: Explicit termination method 'close' not called

07-21 19:33:53.145: E/StrictMode(21289): at dalvik.system.CloseGuard.open(CloseGuard.java:184)

07-21 19:33:53.145: E/StrictMode(21289): at org.apache.harmony.xnet.provider.jsse.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:277)

07-21 19:33:53.145: E/StrictMode(21289): at org.apache.harmony.xnet.provider.jsse.OpenSSLSocketImpl.getSession(OpenSSLSocketImpl.java:738)

07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:92)

07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.conn.ssl.SSLSocketFactory.createSocket(SSLSocketFactory.java:381)

07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:165)

07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164)

07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:119)

07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:360)

07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:670)

07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:509)

07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487)

07-21 19:33:53.145: E/StrictMode(21289): at com.parse.ParseCommand$6.call(ParseCommand.java:425)

07-21 19:33:53.145: E/StrictMode(21289): at com.parse.ParseCommand$6.call(ParseCommand.java:1)

07-21 19:33:53.145: E/StrictMode(21289): at com.parse.Task$3.run(Task.java:225)

07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:390)

07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.FutureTask.run(FutureTask.java:234)

07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:153)

07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)

07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)

07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)
07-21 19:33:53.145: E/StrictMode(21289): at java.lang.Thread.run(Thread.java:841)

--------------------------------------------------------------------------------

7/23.

根据查到的一点资料是..在内部产生了死循环.

因为并发的访问服务器..产生了一些混乱.

所以需要我们建立一个队列.来把并发访问变成串.顺序的访问.
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息
标签: 
相关文章推荐