0

我想知道如何在我的 android 应用程序中处理强制停止。该应用程序在 Activity 中包含一个 asynctask 类，如下所示：

private class SocketTask extends AsyncTask<String, Void, SocketAnswer> {

    ProgressDialog pd;

    @Override
    protected void onPreExecute() {
        super.onPreExecute();
        lockOrientation();
        try {
            if (pd == null) {
                try {
                    pd = new ProgressDialog(MenuDisplayActivity.this);
                } catch (Exception e) {
                }
            }
            pd.setMessage(Global.Labels.get(165).toString());
            pd.setCancelable(false);
            pd.show();
        } catch (Exception e) {
        }           
    }

    public SocketTask(MenuDisplayActivity activity) {
        try {
            pd = new ProgressDialog(activity);
        } catch (Exception e) {
        }
    }

    @Override
    protected SocketAnswer doInBackground(String... params) {

应用程序运行无任何异常，但是，在用户强制停止后（使用三星 Galaxy S5 主页按钮左侧的菜单按钮），当应用程序重新打开时，它会显示“进度对话框”消息请稍候”位于 asynctask 的 onPreExecute 方法中并无限挂起。

当我调试时，我注意到应用程序挂在 Looper 类循环方法中：

public static void loop() {
    final Looper me = myLooper();
    if (me == null) {
        throw new RuntimeException("No Looper; Looper.prepare() wasn't called on this thread.");
    }
    final MessageQueue queue = me.mQueue;

    // Make sure the identity of this thread is that of the local process,
    // and keep track of what that identity token actually is.
    Binder.clearCallingIdentity();
    final long ident = Binder.clearCallingIdentity();

    for (;;) { //The application gets stuck infinitely in this loop
        Message msg = queue.next(); // might block
        if (msg == null) {
            // No message indicates that the message queue is quitting.
            return;
        }

        // This must be in a local variable, in case a UI event sets the logger
        Printer logging = me.mLogging;
        if (logging != null) {
            logging.println(">>>>> Dispatching to " + msg.target + " " +
                    msg.callback + ": " + msg.what);
        }

        msg.target.dispatchMessage(msg);

        if (logging != null) {
            logging.println("<<<<< Finished to " + msg.target + " " + msg.callback);
        }

        // Make sure that during the course of dispatching the
        // identity of the thread wasn't corrupted.
        final long newIdent = Binder.clearCallingIdentity();
        if (ident != newIdent) {
            Log.wtf(TAG, "Thread identity changed from 0x"
                    + Long.toHexString(ident) + " to 0x"
                    + Long.toHexString(newIdent) + " while dispatching to "
                    + msg.target.getClass().getName() + " "
                    + msg.callback + " what=" + msg.what);
        }

        msg.recycle();
    }
}

我们如何确保应用程序摆脱这个无限循环？

谢谢你。

此致。

4

1 回答 1

0

最后通过添加“socketTask.cancel(true);”解决了 到“onDestroy()”方法如下：

@Override
protected void onDestroy() {
    super.onDestroy();
    if (socketTask != null)
        socketTask.cancel(true);
}
于 2015-11-26T14:10:00.023 回答