Well I could be wrong about the cause, but I have definitely seen them stuck before. Killing the process fixed it. It wasn't in production code so I never dug into it.
-Kevin On Feb 28, 11:22 pm, Zsolt Vasvari <[email protected]> wrote: > On Mar 1, 1:01 pm, Kevin TeslaCoil Software <[email protected]> > wrote: > > > I think I've seen something like if you show a toast and then your > > activity is destroyed before the toast disappears it might get stuck. > > Easier to reproduce if you're calling finish(). Probably could avoid > > it if you save the toast reference and do a .cancel() in onDestroy. > > That's absolutely not the case. A lot of my activities finish with a > toast and I've never seen one stuck. -- 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

