good thing hank On Wed, Nov 10, 2010 at 7:41 PM, Hank <[email protected]> wrote: > I managed to fix it, apparently I was not associating the handler and > looper to the child thread > > On Oct 28, 5:22 pm, DanH <[email protected]> wrote: >> Assuming that post() or postDelayed() starts the Thread is even more >> popular. >> >> On Oct 28, 4:47 pm, fadden <[email protected]> wrote: >> >> > On Oct 28, 12:35 pm, DanH <[email protected]> wrote: >> >> > > Lemme guess: You created a Thread but you never started it. >> >> > Calling run() instead of start() is tremendously popular. :-) >> >> > It also causes a memory leak, because Threads get added to ThreadGroup >> > when they're created and don't get removed until they stop executing. >> > If they never start executing, they never get removed. (We're going >> > to change this in a future release to use weak references, which isn't >> > perfect but avoids this situation.) >> >> > > -- > 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
-- 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
