Hey Chris not a bad idea - I will give that a shot. I do see the gc endlessly working during and around the suspension time.
Thanks On Sep 24, 12:29 am, Chris Stratton <cs07...@gmail.com> wrote: > Garbage collecting might suspend your thread. But then so might > trying to write to the log when the garbage collector is also writing > to it. > > If you want to investigate this, I'd try logging time stamps to a pre- > allocated buffer for a while, then dumping them out all at once or > doing some statistics on the interval data. > > On Sep 22, 10:34 am, kypriakos <demet...@ece.neu.edu> wrote:> Hi all, > > > Are there any limits on the number of threads or any constraints > > on how the emulator (under Eclipse) schedules the application > > threads? I get suspended threads that don't really wait on anything > > but rather get bumped out from execution time ... I will try using the > > Debug class to get some statistics on the thread alloc etc. even > > though > > the DDMS does that already. > > > One example is, I have a simple class that simply prints a '.' every > > 3 seconds - well, the LogCat shows the emulator collecting garbage > > objects but the thread is suspended and does not print the '.' ... I > > may > > be missing something simple here > > > Thanks -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
