Watchdog in system server (lockCanvasNative?)

[Tomei]

Hello,

We are running some stress tests on a 2.1-based handset, and from time
to time, when launching a large number of apps, we see this:


09-28 11:11:27.899 2202 2447 I Watchdog: Watchdog is killing the
system process

From the ANR traces.txt, we see that all loopers are idle, except the
following 3 -- It looks like lockCanvasNative has been blocked, which
prevents the watchdog HeartbeatHandler from executing.

My question is -- does lockCanvasNative ever block indefintely (or
some sort of starvation scenarios)?


============================
"android.server.ServerThread" prio=5 tid=15 NATIVE
| group="main" sCount=1 dsCount=0 s=Y obj=0x47e01b98 self=0x13bbc8
| sysTid=2218 nice=-2 sched=0/0 cgrp=default handle=1293536
at android.view.Surface.lockCanvasNative(Native Method)
at android.view.Surface.lockCanvas(Surface.java:297)
at android.view.ViewRoot.draw(ViewRoot.java:1290)
at android.view.ViewRoot.performTraversals(ViewRoot.java:1121)
at android.view.ViewRoot.handleMessage(ViewRoot.java:1640)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at com.android.server.ServerThread.run(SystemServer.java:541)

"ActivityManager" prio=5 tid=17 NATIVE
| group="main" sCount=1 dsCount=0 s=Y obj=0x47e0c508 self=0x124158
| sysTid=2219 nice=-2 sched=0/0 cgrp=default handle=1303272
at android.os.Process.sendSignal(Native Method)
at
com.android.server.am.ActivityManagerService.appNotRespondingLocked(ActivityManagerService.java:
4703)
at
com.android.server.am.ActivityManagerService.broadcastTimeout(ActivityManagerService.java:
12240)
at com.android.server.am.ActivityManagerService.access
$300(ActivityManagerService.java:126)
at com.android.server.am.ActivityManagerService
$2.handleMessage(ActivityManagerService.java:1087)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at com.android.server.am.ActivityManagerService
$AThread.run(ActivityManagerService.java:1335)

"ConnectivityThread" prio=5 tid=47 RUNNABLE
| group="main" sCount=1 dsCount=0 s=Y obj=0x483f0d58 self=0x3c9468
| sysTid=2423 nice=0 sched=0/0 cgrp=default handle=3593520
at
android.app.ActivityThread.getApplicationThread(ActivityThread.java:~2218)
at
android.app.ApplicationContext.sendBroadcast(ApplicationContext.java:
699)
at
android.net.wifi.WifiStateTracker.handleMessage(WifiStateTracker.java:
1226)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at com.android.server.ConnectivityService
$ConnectivityThread.run(ConnectivityService.java:200)
============================

[Dianne Hackborn]

It shouldn't.  For the watchdog to go off, something must be very broken -- it waits for at least a minute, so this means your system process has been hung to some degree for at least a minute.

Getting stuck in lockCanvasNative is an issue with surface flinger or below...  and more likely below, such as in OpenGL drivers.

--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To post to this group, send email to android-...@googlegroups.com.
To unsubscribe from this group, send email to android-platfo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-platform?hl=en.

--
Dianne Hackborn
Android framework engineer
hac...@android.com

Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails.  All such questions should be posted on public forums, where I and others can see and answer them.

[Michael Wu]

I met the same issue. This often appears when swapping launcher and drawer. Is this possible a known issue on android framework?

2010/9/29 Dianne Hackborn <hac...@android.com>

--
Michael Wu