LogCat每5秒在SyncProcessorQueue中显示异常


8

我刚开始在Logcat中注意到这一点,似乎每5秒钟就会捕获一次此异常。有谁知道它可能是什么应用程序或操作系统的一部分?我无法想象它会不断运行,并且抛出异常对我的电池有好处,无论屏幕是打开还是关闭都会发生这种情况。

手机是moto Atrix,android 2.3

我想知道是com.google.apps.dots什么吗?

04-19 17:51:47.455: E/SyncProcessorQueue(27593): Caught unexpected error
04-19 17:51:47.455: E/SyncProcessorQueue(27593): java.lang.NullPointerException
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.provider.BlobStore.addToPossibleStores(BlobStore.java:98)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.provider.BlobStore.getPossibleStores(BlobStore.java:108)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.CleanUpSync$OldAttachmentAndBlobCleanUp.syncSelf(CleanUpSync.java:138)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.BaseSyncNode.syncSelfInternal(BaseSyncNode.java:121)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.BaseSyncNode.sync(BaseSyncNode.java:104)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.BaseSyncNode.syncNextChild(BaseSyncNode.java:196)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.BaseSyncNode.sync(BaseSyncNode.java:107)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.BaseSyncNode.syncNextChild(BaseSyncNode.java:196)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.BaseSyncNode.sync(BaseSyncNode.java:107)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.BaseSyncNode.syncNextChild(BaseSyncNode.java:196)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.BaseSyncNode.sync(BaseSyncNode.java:107)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.BaseSyncNode.syncNextChild(BaseSyncNode.java:196)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.BaseSyncNode.sync(BaseSyncNode.java:107)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.SyncNodeProcessor.syncNextNode(SyncNodeProcessor.java:34)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.SyncProcessorQueue.process(SyncProcessorQueue.java:134)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.SyncProcessorQueue.process(SyncProcessorQueue.java:114)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.SyncProcessorQueue.access$200(SyncProcessorQueue.java:31)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at com.google.apps.dots.android.app.sync.SyncProcessorQueue$Processor.run(SyncProcessorQueue.java:236)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:444)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:306)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1088)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:581)
04-19 17:51:47.455: E/SyncProcessorQueue(27593):    at java.lang.Thread.run(Thread.java:1019)

1
根据我在其他日志中看到的内容,我认为这可能与Google Currents有关。你有安装吗?
eldarerathis 2012年

@eldarerathis,是的,已安装。感谢您的注意。
蒂姆(Tim)

它的包名称就在这里-“ com.google.apps.dots”之后的所有内容都是该错误的类以及相关的类。com.google.android.apps.currents是Currents的程序包名称。如果您可以摆脱该软件包,则应该可以解决该问题。-
RM-中联

Play商店中可能已经有一个更新,该更新修复了空指针异常...
t0mm13b 2012年

Answers:


2

按照线程,它与Google Currents有关。要么禁用Currents的自动同步功能,要么完全卸载Currents以摆脱此错误。

我认为这不是一个“严重”错误,也不应引起任何其他问题(例如电池电量耗尽等)。

By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.