service的启动不能超过10s。

最新推荐文章于 2025-05-02 09:42:10 发布

原创最新推荐文章于 2025-05-02 09:42:10 发布 · 1.1k 阅读

0 ·

CC 4.0 BY-SA版权

Android客户端专栏收录该内容

2 篇文章

订阅专栏

本文记录了一次在Android应用中启动Service时遇到的ANR（应用无响应）问题。通过详细的错误日志分析发现，Service启动时CPU使用率异常高，并导致了后台进程被杀。最终通过将Service启动逻辑放置到子线程中执行的方式成功解决问题。

在android启动的时候，我们开启一个service，结果在启动过程中报错。出现了如下的异常信息。然后，我们将启动的执行代码放到thread运行，就解决了问题。

08-08 09:22:17.820: E/ActivityManager(2099): ANR in com.ztao.printer.server

08-08 09:22:17.820: E/ActivityManager(2099): Reason: Executing service com.ztao.printer.server/.core.PrinterService
08-08 09:22:17.820: E/ActivityManager(2099): Load: 2.24 / 0.98 / 0.37
08-08 09:22:17.820: E/ActivityManager(2099): CPU usage from 14658ms to 0ms ago:
08-08 09:22:17.820: E/ActivityManager(2099):   95% 1921/sdcard: 51% user + 43% kernel / faults: 82 minor
08-08 09:22:17.820: E/ActivityManager(2099):   4.1% 2334/android.process.media: 2.5% user + 1.6% kernel / faults: 280 minor
08-08 09:22:17.820: E/ActivityManager(2099):   0.3% 2099/system_server: 0% user + 0.2% kernel / faults: 21 minor
08-08 09:22:17.820: E/ActivityManager(2099):   0% 1914/gpsd: 0% user + 0% kernel
08-08 09:22:17.820: E/ActivityManager(2099):   0% 4636/android.process.acore: 0% user + 0% kernel / faults: 72 minor
08-08 09:22:17.820: E/ActivityManager(2099):   0% 1276/kworker/0:2: 0% user + 0% kernel
08-08 09:22:17.820: E/ActivityManager(2099):   0% 1922/adbd: 0% user + 0% kernel
08-08 09:22:17.820: E/ActivityManager(2099):   0% 2427/com.sec.android.app.sysscope: 0% user + 0% kernel / faults: 8 minor
08-08 09:22:17.820: E/ActivityManager(2099):   0% 4839/com.google.process.gapps: 0% user + 0% kernel
08-08 09:22:17.820: E/ActivityManager(2099):   0% 4949/com.sina.weibo: 0% user + 0% kernel / faults: 30 minor
08-08 09:22:17.820: E/ActivityManager(2099): 100% TOTAL: 54% user + 45% kernel
08-08 09:22:17.820: E/ActivityManager(2099): CPU usage from 698ms to 1221ms later with 99% awake:
08-08 09:22:17.820: E/ActivityManager(2099):   92% 1921/sdcard: 52% user + 39% kernel / faults: 3 minor
08-08 09:22:17.820: E/ActivityManager(2099):     90% 1932/sdcard: 52% user + 37% kernel
08-08 09:22:17.820: E/ActivityManager(2099):   5.7% 2334/android.process.media: 1.9% user + 3.8% kernel / faults: 8 minor
08-08 09:22:17.820: E/ActivityManager(2099):     5.7% 3788/MediaScannerSer: 1.9% user + 3.8% kernel
08-08 09:22:17.820: E/ActivityManager(2099):   3.7% 2099/system_server: 0% user + 3.7% kernel
08-08 09:22:17.820: E/ActivityManager(2099):     1.8% 2136/ActivityManager: 0% user + 1.8% kernel
08-08 09:22:17.820: E/ActivityManager(2099):   1% 2946/cn.opda.a.phonoalbumshoushou: 0% user + 1% kernel / faults: 1 minor
08-08 09:22:17.820: E/ActivityManager(2099): 100% TOTAL: 57% user + 42% kernel
08-08 09:22:17.820: W/ActivityManager(2099): Killing ProcessRecord{42af8f90 5030:com.ztao.printer.server/10116}: background ANR
08-08 09:22:17.830: I/ActivityManager(2099): Process com.ztao.printer.server (pid 5030) has died.
08-08 09:22:17.830: W/ActivityManager(2099): Scheduling restart of crashed service com.ztao.printer.server/.core.PrinterService in 248624ms
08-08 09:22:17.835: I/power(2099): *** acquire_dvfs_lock : lockType : 1 freq : 1000000