本文介绍了" AndroidRuntime:关闭VM"没有别的的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

由于某些原因,LogCat中未报告任何堆栈跟踪了上崩溃。相反,我只得到了以下信息:

For some reason, LogCat doesn't report any stack traces anymore on crashes. Instead, I only get the following info:

D/AndroidRuntime: Shutting down VM
W/dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x40dd3960)

这是很奇怪,因为我一直在非常相同的项目三个月,直到最近(二,三天前)堆栈跟踪停止显示。这是什么原因?我怎样才能得到它再次显示堆栈跟踪?

This is really weird because I've been working on the very same project for three months, and only recently (two, three days ago) the stack traces stopped showing. What could cause this? How can I get it to show stack traces again?

推荐答案

我经历了同样的问题。升级谷歌Analytics(分析),以7版本后(或7.3,我不记得了),我的应用程序总是遇到错误时没有关闭任何logcat的消息。

I experienced the same problem. After upgrading Google Analytics to version 7 (or 7.3, I do not remember), my app always closes without any logcat messages when encountering an error.

事实证明,它发生,如果我同时启用自定义捕获所有异常进行处理(发#setUncaughtExceptionHandler ),并在谷歌Analytics(分析)报告中死机功能。

It turns out that it happens if I enable both a custom catch-all-exception handler (Thread#setUncaughtExceptionHandler) and the report crash feature in Google Analytics.

当我关闭其中的一个,在l​​ogcat中再次显示堆栈跟踪。

When I disable one of them, the logcat displays the stack trace again.

这篇关于" AndroidRuntime:关闭VM"没有别的的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-16 01:37