java - 重新打开时强制关闭

Question

我的应用程序遇到问题，当它被电话中断或按下主页键时，它会强制关闭。当用户返回应用程序时，他们会收到强制关闭消息。我已阅读以下问题并尝试回答建议:Force Close when opening app after pressing home button在这里:Android crash when app is closed and reopened 。第二个问题中提出的答案没有帮助，当我添加 wait() 时，它在应用程序打开时强制关闭，当我添加 notification() 时，当我离开应用程序时，它强制关闭。我没有想法，现在正在寻找，看看是否有人可以解决这个问题。

我正在使用带有 LunarLander 使用的 surfaceCreated 和 surfaceDestroyed 方法的表面 View 。

提前致谢。

日志猫:

Log1:<br>
07-08 02:18:32.284: ERROR/AndroidRuntime(627): Uncaught handler: thread main exiting due to uncaught exception
07-08 02:18:32.354: ERROR/AndroidRuntime(627): java.lang.IllegalThreadStateException: Thread already started.
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at java.lang.Thread.start(Thread.java:1322)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at com.android.hitmanassault.HitmanView.surfaceCreated(HitmanView.java:115)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at android.view.SurfaceView.updateWindow(SurfaceView.java:454)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at android.view.SurfaceView.onWindowVisibilityChanged(SurfaceView.java:189)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at android.view.View.dispatchWindowVisibilityChanged(View.java:3782)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at android.view.ViewGroup.dispatchWindowVisibilityChanged(ViewGroup.java:692)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at android.view.ViewGroup.dispatchWindowVisibilityChanged(ViewGroup.java:692)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at android.view.ViewRoot.performTraversals(ViewRoot.java:706)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at android.view.ViewRoot.handleMessage(ViewRoot.java:1633)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at android.os.Handler.dispatchMessage(Handler.java:99)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at android.os.Looper.loop(Looper.java:123)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at android.app.ActivityThread.main(ActivityThread.java:4363)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at java.lang.reflect.Method.invokeNative(Native Method)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at java.lang.reflect.Method.invoke(Method.java:521)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
07-08 02:18:32.354: ERROR/AndroidRuntime(627):     at dalvik.system.NativeStart.main(Native Method)

日志2:

07-08 02:21:39.805: ERROR/AndroidRuntime(663): Uncaught handler: thread main exiting due to uncaught exception
07-08 02:21:39.854: ERROR/AndroidRuntime(663): java.lang.IllegalMonitorStateException: object not locked by thread before notify()
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at java.lang.Object.notify(Native Method)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at com.android.hitmanassault.HitmanView.surfaceDestroyed(HitmanView.java:135)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at android.view.SurfaceView.reportSurfaceDestroyed(SurfaceView.java:488)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at android.view.SurfaceView.updateWindow(SurfaceView.java:413)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at android.view.SurfaceView.onWindowVisibilityChanged(SurfaceView.java:189)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at android.view.View.dispatchWindowVisibilityChanged(View.java:3782)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at android.view.ViewGroup.dispatchWindowVisibilityChanged(ViewGroup.java:692)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at android.view.ViewGroup.dispatchWindowVisibilityChanged(ViewGroup.java:692)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at android.view.ViewRoot.performTraversals(ViewRoot.java:706)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at android.view.ViewRoot.handleMessage(ViewRoot.java:1633)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at android.os.Handler.dispatchMessage(Handler.java:99)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at android.os.Looper.loop(Looper.java:123)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at android.app.ActivityThread.main(ActivityThread.java:4363)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at java.lang.reflect.Method.invokeNative(Native Method)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at java.lang.reflect.Method.invoke(Method.java:521)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
07-08 02:21:39.854: ERROR/AndroidRuntime(663):     at dalvik.system.NativeStart.main(Native Method)

SurfaceDestroyed 方法:

public void surfaceDestroyed(SurfaceHolder holder) {
        Log.d(TAG, "Surface is being destroyed");   
        boolean retry = true;
        thread.setRunning(false);
        thread.notify();
        while (retry) {
            try {
                thread.join();
                                //thead.notify();  ---I would get rid of the join part
                retry = false;  
            } catch (InterruptedException e) {
                // TODO Auto-generated catch block
                e.printStackTrace();
            }               
        }
        Log.d(TAG, "Thread was shut down cleanly");
    }

SurfaceCreated 方法:

public void surfaceCreated(SurfaceHolder holder) {
        thread.initLevel();
        thread.setRunning(true);    
        thread.start();
                //thread.notify();      
    }

编辑:
我在尝试用通知进行切换的地方，等待。我还尝试将“通知”放在“尝试”之前，并将“等待”放在“连接”位置。

Answer 1

强制关闭的应用程序始终会生成可以在 logcat 缓冲区中看到的堆栈跟踪。如果您的应用程序强制关闭，堆栈跟踪的顶部将包含应用程序内的类之一，标记触发崩溃的行号。

调查该行号以查看出了什么问题。 (要获得更详细的答案，您还可以通过更新您的问题以包含导致崩溃的堆栈跟踪和代码来提供更多详细信息。)

通过使用正确的异常处理和编码，应用程序应该很少崩溃(除非 Android 子系统导致您的应用程序崩溃)。

就您而言，您有几个线程问题。

您不能两次启动同一个线程，并且在调用线程上的等待之前不能调用notify。必须在同步方法/ block 中调用 wait()、notify()、notifyAll() 也是一个好习惯。(有关更多信息，请参阅此:http://www.xyzws.com/Javafaq/why-wait-notify-notifyall-must-be-called-inside-a-synchronized-method-block/127)

我还建议阅读一些有关 Java 并发性的文章:http://www.javaconcurrencyinpractice.com/