Android的 - 进程死亡问题 [英] Android - Process Has Died Issue

问题描述

应用程序只是崩溃，并完成活动没有太多的信息。

Application simply crashes and finishes the activity without much info.

04-01 13:30:43.739: W/AudioService(180): setMode() client died
04-01 13:30:43.739: W/GpsLocationProvider(180): Unneeded remove listener for uid 1000
04-01 13:30:43.739: D/libloc(180): loc_eng_stop called
04-01 13:30:43.739: I/ActivityManager(180): Process com.company.android (pid 2590)has died.
04-01 13:30:43.739: W/ActivityManager(180): Scheduling restart of crashed service com.company.android/.utilities.OurGPSService in 80000ms

日志检索的要少得多，它只是表明，该工艺刚刚去世，使我们的全球定位系统服务重新启动。它是一些NDK崩溃或一些相关的MediaPlayer的？请确定该问题有所帮助。

Log retrieved is much less, it simply shows that the process just died and causes our GPS Service to restart. Is it some ndk crash or something related to MediaPlayer? Please help in identifying the issue.

推荐答案

我发现了2个不同的答案类似的问题：

I found 2 different answers to similar questions:

• ActivityManager进程已经死亡问题
  • 引用一个Android bug报告从不同的线程重复使用位图
  • 称，这可能仅仅是正常的行为在某些情况下

  要加入到这一点，我在追崩溃，其中 ApplicationManager 抛出一个 ClassCastException异常从Android框架内。它不仅是因为我知道我做了一定的黑客，我是能够确定跟踪的那一部分是我的应用程序。

  To add to this, I was chasing a crash where the ApplicationManager throws a ClassCastException from within the Android framework. Its only because I know I did a certain hack that I was able to determine that part of the trace was for my app.

  我得到的教训是，有时崩溃日志有没有证据证明你的应用程序的名称。 （另一个教训是，黑客总是回来咬黑客...）

  The lesson I learnt is that sometimes the crash log has no evidence of your app's name. (The other lesson is that hacks always come back to bite the hacker...)

  这篇关于Android的 - 进程死亡问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！