主线程工作太多，应用程序冻结答案

【问题标题】：Too much work in main thread, app freezes主线程工作太多，应用程序冻结
【发布时间】：2014-02-26 17:54:34
【问题描述】：

我在这里调用了一个 Activity，它是一个聊天应用程序。

猫日志：

02-26 12:30:38.996: I/Choreographer(807): Skipped 35 frames!  The application may be doing too much work on its main thread.
02-26 12:30:39.196: I/Choreographer(807): Skipped 31 frames!  The application may be doing too much work on its main thread.
02-26 12:30:39.516: I/Choreographer(807): Skipped 31 frames!  The application may be doing too much work on its main thread.
02-26 12:30:39.996: I/Choreographer(807): Skipped 32 frames!  The application may be doing too much work on its main thread.
02-26 12:30:40.066: I/Choreographer(807): Skipped 37 frames!  The application may be doing too much work on its main thread.
02-26 12:30:40.207: I/Choreographer(807): Skipped 33 frames!  The application may be doing too much work on its main thread.
02-26 12:30:40.896: I/Choreographer(807): Skipped 33 frames!  The application may be doing too much work on its main thread.
02-26 12:30:41.586: I/Choreographer(807): Skipped 30 frames!  The application may be doing too much work on its main thread.
02-26 12:30:42.266: I/Choreographer(807): Skipped 30 frames!  The application may be doing too much work on its main thread.
02-26 12:30:42.486: I/Choreographer(807): Skipped 31 frames!  The application may be doing too much work on its main thread.
02-26 12:30:42.556: I/Choreographer(807): Skipped 37 frames!  The application may be doing too much work on its main thread.
02-26 12:30:42.826: I/Choreographer(807): Skipped 32 frames!  The application may be doing too much work on its main thread.
02-26 12:30:43.316: I/Choreographer(807): Skipped 30 frames!  The application may be doing too much work on its main thread.
02-26 12:30:43.777: I/Choreographer(807): Skipped 30 frames!  The application may be doing too much work on its main thread.
02-26 12:30:43.826: I/Choreographer(807): Skipped 32 frames!  The application may be doing too much work on its main thread.
02-26 12:30:43.866: I/Choreographer(807): Skipped 34 frames!  The application may be doing too much work on its main thread.
.   .      .   .      .  
.   .      .   .      .
.   .      .   .      .

这就是我从 MainActivity 开始活动的方式：

public class MainActivity extends Activity {
     Handler handler;
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);

    Button b = (Button) findViewById(R.id.button1);
     handler = new Handler(Looper.getMainLooper());


    b.setOnClickListener(new View.OnClickListener() {
        public void onClick(View v) {
            final  Intent i = new Intent(com.example.mainactivity.MainActivity.this,com.quickblox.sample.chat.ui.activities.SplashActivity.class);
             handler.post(new Runnable() {
                    @Override
                    public void run() {
                        startActivity(i);
                    }
                });

如何防止这种情况，调用活动后应用程序挂起。什么问题？

更新：

SplashActivity：

public class SplashActivity extends Activity implements QBCallback {

    private static final String APP_ID = "7467";
    private static final String AUTH_KEY = "TxRFWfX8tTXQ4gv";
    private static final String AUTH_SECRET = "y-QJrO2j69VTaCs";

    private ProgressBar progressBar;

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_splash);

        progressBar = (ProgressBar) findViewById(R.id.progressBar);

        QBSettings.getInstance().fastConfigInit(APP_ID, AUTH_KEY, AUTH_SECRET);
        QBAuth.createSession(this);
    }

    @Override
    public void onComplete(Result result) {
        progressBar.setVisibility(View.GONE);

        if (result.isSuccess()) {
            Intent intent = new Intent(this, MainActivity.class);
            startActivity(intent);
            finish();
        } else {
            AlertDialog.Builder dialog = new AlertDialog.Builder(this);
            dialog.setMessage("Error(s) occurred. Look into DDMS log for details, " +
                    "please. Errors: " + result.getErrors()).create().show();
        }
    }

    @Override
    public void onComplete(Result result, Object context) {
    }
}

更新：

您可以在this 线程中找到详细信息。

【问题讨论】：

你不需要发帖 Runnable 来做你正在做的事情。
你能展示 SplashActivity 的 onCreate() 方法吗？很可能没有及时完成。
我认为 Yakiv 是正确的。对 QBSettings 和 QBAuth 的调用最好在后台线程或通过 AsyncTask 运行，以便 onCreate() 可以快速完成。
我同意@NigelK，使用 AsyncTask 来执行 HTTP 请求。
我试过了，但是这个问题已经被 API @SQLiteNoob 解决了

标签： android

【解决方案1】：

startActivity(i); 只需向系统发送一个 Intent。所以你不需要在单独的线程中启动活动。

相反，您应该在另一个线程中从SplashActivity onCreate 方法中完成所有辛勤工作。

public class MainActivity extends Activity {
//...
 @Override
 protected void onCreate(Bundle savedInstanceState) {
   //...
   final  Intent intent = new Intent(this,SplashActivity.class);
   startActivity(intent);
 }
}

public class SplashActivity extends Activity {
//...
 @Override
 protected void onCreate(Bundle savedInstanceState) {
   //...
   new Thread(new Runnable()
   {
     @Override
     public void run() {
      //do loading data or whatever hard here

      runOnUiThread(new Runnable(){
        @Override
        public void run() {
          //..update your UI here
        }
      });
     }
   }).start();
 }
}

请记住，您只能在 Main Android（通常称为 UI）线程上更新您的 UI。

我建议您的 QBAuth.createSession(this); 正在打开某种 Http 连接，这就是您的应用程序冻结的原因。将其移至单独的线程。

更新：

public class SplashActivity extends Activity{

private static final String APP_ID = "7467";
private static final String AUTH_KEY = "TxRFWfX8tTXQ4gv";
private static final String AUTH_SECRET = "y-QJrO2j69VTaCs";

public static class QBAuth{
    private static QBCallback mQBCallback;

    public static void createSession(QBCallback qbCallback) {
        // do request initialization
        mQBCallback = qbCallback;
    }
}

public interface QBCallback{
    public void onComplete(Result result);
    public void onComplete(Result result, Object context);
}

public class Result{
    boolean isSuccess;
    String errors;

    public boolean isSuccess() {
        return isSuccess;
    }

    public void setSuccess(boolean isSuccess) {
        this.isSuccess = isSuccess;
    }

    public String getErrors() {
        return errors;
    }

    public void setErrors(String errors) {
        this.errors = errors;
    }
}

private ProgressBar progressBar;

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_splash);

    progressBar = (ProgressBar) findViewById(R.id.progressBar);


    new Thread(new Runnable() {
        @Override
        public void run() {
            QBSettings.getInstance().fastConfigInit(APP_ID, AUTH_KEY, AUTH_SECRET);
            QBAuth.createSession(mQBCallback);
        }
    });
}


private QBCallback mQBCallback = new QBCallback() {
    @Override
    public void onComplete(Result result) {
        handleResult(result);
    }

    @Override
    public void onComplete(Result result, Object context) {

    }
};

private void handleResult(final Result result) {
    runOnUiThread(new Runnable() {
        @Override
        public void run() {
            progressBar.setVisibility(View.GONE);

            if (result.isSuccess()) {
                Intent intent = new Intent(SplashActivity.this, MainActivity.class);
                startActivity(intent);
                finish();
            } else {
                AlertDialog.Builder dialog = new AlertDialog.Builder(SplashActivity.this);
                dialog.setMessage("Error(s) occurred. Look into DDMS log for details, " +
                        "please. Errors: " + result.getErrors()).create().show();
            }
        }
    });
}
}

【讨论】：

仍然是相同的结果，并且QBAuth.createSession(this) 将QBAuth.createSession(NULL,this) 作为Runnable 中的参数。这样可以吗？
我觉得这个错误可能在其他地方？
更新：应该是QBAuth.createSession(mCallBack);
你的QBCallback函数还好吗？
...嘿，您真的希望我在这里创建您的任务的工作样本吗？我已经解释了您在记事本中创建的快速示例的问题，展示了如何处理它（是的，有一些语法错误，如this 必须是SplashActivity.this）。在尝试开发 Android 应用程序之前，您应该学习一些 Java 语法。我刚刚创建了您的模型的模型，并在答案中向您展示了它的示例（那里没有语法错误，在 IDE 中检查）。检查更新。干杯

【解决方案2】：

首先，主要活动中的处理程序完全没用。 onClick 回调由系统在 UI 线程上调用，并且您的处理程序也绑定到 UI 线程，因此您可以不使用它。但我怀疑您是否遇到了问题，这只是一个很小的开销。

您可能想尝试转移呼叫

QBSettings.getInstance().fastConfigInit(APP_ID, AUTH_KEY, AUTH_SECRET);
QBAuth.createSession(this);

到后台线程，但他们可能期望在 UI 线程上被调用，这会导致一些问题。

由于您的代码与此处的代码是 1:1 的：https://github.com/QuickBlox/quickblox-android-sdk/tree/master/sample-chat，我将首先尝试示例应用程序来检查问题是否也可以在那里看到。如果是，只需在 github 项目中打开一个问题 :)

如果不是，那么您正在做一些不同的事情，我们将需要更多代码来调查...

【讨论】：

感谢您的回复。我运行了示例，效果很好。quickBlox 的人告诉我已经配置为在另一个线程中运行，所以不需要额外的工作。

【解决方案3】：

尝试改变：

android:label="@string/app_name"

从您调用的活动中剪切，并粘贴到您的启动器活动中。

<activity android:name="com.quickblox.sample.chat.Launch"
 android:label="@string/app_name">
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
</activity>

【讨论】：