On Feb 16, 8:07 am, Bill Tschumy <[email protected]> wrote: > Anytime the LogCat shows a GC_FOR_MALLOC or a GC_EXTERNAL_ALLOC, the app > hangs with OpenGL in this LockCondition. It appears that GC_EXPLICT, for the > most part, does not cause a problem (maybe these are smaller allocs, I don't > know).
The cause indicates whether the GC happened because you ran out of memory while allocating an object (FOR_MALLOC), while performing an "external allocation" (EXTERNAL_ALLOC), or explicitly as the result of calling System.gc() (EXPLICIT). The actions performed by the GC won't be much different. > Searching the internet, it seems that people are reporting things like this > on the HTC phones. Usually they say the problem is very sporadic and hard to > reproduce. I can reproduce it easily by simply putting a System.gc() call > into my application flow or by doing something that allocates a chunk of > memory forcing the GC to run. If you have an APK that demonstrates the problem, please file a bug on b.android.com and attach it. The "waitForCondition" lockup could be due to any number of things, including GL driver bugs. See also http://code.google.com/p/android/issues/detail?id=10505 . -- 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

