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

检索到的日志要少得多，它只是表明进程刚刚结束并导致我们的 GPS 服务重新启动.是 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 错误报告
  • 声称在某些情况下这只是正常行为

  此外，我正在追赶 ApplicationManager 从 Android 框架内抛出 ClassCastException 的崩溃.只是因为我知道我做了某种 hack，我才能够确定跟踪的那部分是针对我的应用程序的.

  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屋！