Hey Jason, it's running in the foreground - that's why this was a bit troubling. Do you have a large number of threads running in your case (100+)?
Thanks On Sep 22, 1:59 pm, Jason <[email protected]> wrote: > Is your app running in the foreground during all of this? I have > threads running continuously without any issues. > > If your app is NOT running in the foreground then it may well be > suspended by the platform. As a "general" rule the onPause method of > an Activity should also gracefully pause your threads. > > If you need to be running continuously in the background then you > probably need a Service: > > http://developer.android.com/reference/android/app/Service.html > > On Sep 23, 12:34 am, kypriakos <[email protected]> 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 [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
