Hello all, I have a question regarding the following logcat warnings:

SurfaceFlinger: executeScheduledBroadcasts() skipped, contention on
the client. We'll try again later...
SurfaceComposerClient: lock_layer timed out (is the CPU pegged?)
layer=1, lcblk=0x424800a0, state=00000003 (was 00000013)
SurfaceComposerClient: lock_layer() timed out but didn't appear to
need to be locked and we recovered (layer=1, lcblk=0x424800a0,
state=00000003)

I'm running my game on a dev phone, using sdk 1.6, using a
GLSurfaceView and renderer for my drawing, and a separate thread for
my logic (I heard this may be a thread issue?).

 At any rate, I experience no crashes, or major performance issues,
other than an occasional gc. If I let the application sit idle for a
few mins, LogCat will be full of the above mentioned warnings. Does
anyone know if this is a code issue, normal behavior, or some kind of
documented bug? I apologize if this has been addressed already, but I
have had little luck in tracking down information.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to