主线程调用HttpURLConnection.getResponseCode()引发ANR问题求助

问题描述 #

我在Google Play控制台收到大量ANR报告，却无从下手排查。已经用try-catch包裹问题代码，但程序仍卡在特定代码行，且无法复现该问题，求助懂相关异常与代码的人士提供解决方案。

问题代码 #

private static boolean urlExists(String urlString) {
    HttpURLConnection huc;
    try {
        URL url = new URL(urlString);
        huc = (HttpURLConnection) url.openConnection();
        huc.setRequestMethod("HEAD");
        int responseCode = huc.getResponseCode(); // 第246行，问题发生处
        return responseCode != 404;
    } catch (IOException e) {
        e.printStackTrace();
    }
    return false;
}

ANR报告内容 #

Thread

"main" tid=1 Native

  #00  pc 0x000000000009b114  /apex/com.android.runtime/lib/bionic/libc.so (recvfrom+16)
  #01  pc 0x000000000001aceb  /apex/com.android.art/lib/libopenjdk.so (NET_Read+36)
  #02  pc 0x000000000001b3d5  /apex/com.android.art/lib/libopenjdk.so (SocketInputStream_socketRead0+176)
  at java.net.SocketInputStream.socketRead0 (Native method)
  at java.net.SocketInputStream.socketRead (SocketInputStream.java:118)
  at java.net.SocketInputStream.read (SocketInputStream.java:173)
  at java.net.SocketInputStream.read (SocketInputStream.java:143)
  at com.android.okhttp.okio.Okio$2.read (Okio.java:138)
  at com.android.okhttp.okio.AsyncTimeout$2.read (AsyncTimeout.java:213)
  at com.android.okhttp.okio.RealBufferedSource.indexOf (RealBufferedSource.java:307)
  at com.android.okhttp.okio.RealBufferedSource.indexOf (RealBufferedSource.java:301)
  at com.android.okhttp.okio.RealBufferedSource.readUtf8LineStrict (RealBufferedSource.java:197)
  at com.android.okhttp.internal.http.Http1xStream.readResponse (Http1xStream.java:188)
  at com.android.okhttp.internal.http.Http1xStream.readResponseHeaders (Http1xStream.java:129)
  at com.android.okhttp.internal.http.HttpEngine.readNetworkResponse (HttpEngine.java:750)
  at com.android.okhttp.internal.http.HttpEngine.readResponse (HttpEngine.java:622)
  at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute (HttpURLConnectionImpl.java:475)
  at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getResponse (HttpURLConnectionImpl.java:411)
  at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getResponseCode (HttpURLConnectionImpl.java:542)
  at mycompany.mypackage.images.ImageFetcher.urlExists (ImageFetcher.java:246)

解决方案 #

核心原因 #

ANR的根源是在主线程执行网络IO操作。从日志可以看到urlExists方法运行在主线程（"main" tid=1），getResponseCode()会阻塞线程等待服务器响应，一旦网络卡顿、服务器无响应，等待时间超过Android主线程的5秒限制，就会触发ANR。try-catch只能捕获IO异常，解决不了线程阻塞问题。

具体修复措施 #

• 强制将网络请求移到子线程
  绝对不能在主线程调用urlExists方法，用线程池、Coroutine（Kotlin）或AsyncTask执行：

  // 定义全局线程池
  private static final ExecutorService NETWORK_EXECUTOR = Executors.newSingleThreadExecutor();
  
  // 调用示例
  NETWORK_EXECUTOR.execute(() -> {
      boolean isUrlValid = urlExists("目标URL");
      // 将结果回调到主线程处理（比如更新UI）
      new Handler(Looper.getMainLooper()).post(() -> {
          // 处理结果逻辑
      });
  });
  

• 设置网络超时时间
  即使在子线程，也要给HttpURLConnection设置超时，避免无限等待：

  huc.setConnectTimeout(5000); // 连接超时5秒
  huc.setReadTimeout(5000);    // 读取响应超时5秒
  

• 替换HttpURLConnection（可选）
  改用OkHttp这类成熟网络库，默认支持线程调度和超时配置，代码更健壮：

  private static boolean urlExists(String urlString) {
      OkHttpClient client = new OkHttpClient.Builder()
              .connectTimeout(5, TimeUnit.SECONDS)
              .readTimeout(5, TimeUnit.SECONDS)
              .build();
      Request request = new Request.Builder()
              .url(urlString)
              .head()
              .build();
      try (Response response = client.newCall(request).execute()) {
          return response.code() != 404;
      } catch (IOException e) {
          return false;
      }
  }
  

• 优化异常处理逻辑
  原代码的e.printStackTrace()仅打印日志，无实际错误处理，直接返回false更合理，避免无效等待。

复现问题的方法 #

本地难以复现是因为网络环境稳定，可通过以下方式模拟：

• 用Android Studio的Network Profiler设置弱网（比如2G网络）
• 用Charles代理设置请求延迟
• 断开网络后调用方法，观察是否阻塞

内容的提问来源于stack exchange，提问作者mcfly soft