Hm, I am getting the same behavior and waste a lot of time to understand why activity is created twice and didn't succeed. Am pretty sure that this is because dealing with async task, but I can't understand where the problem.
Is there any way to find out why activity was created - stacktrace doesn't show me anything interesting. May be intent analyzing can help me? Please say where to look. On Jul 2, 11:07 pm, skink <[email protected]> wrote: > skink wrote: > > hi, > > > i just made another interesting observation: when and only when > > changing from landscape to portrait mode the screen dims a bit and the > > system sometimes calls my Activity twice: the first Activity is > > getting normal Activity life cycle but its onDestroy()ed in fraction > > of seconds, and then the second Activity is created and works as > > expected. i think that is the first 'temp' Activity that leaks. anyone > > had the same case? > > > thanks > > pskink > > i found my leak - it was my foult - i was registering idle handler in > onCreate letting it auto-unregister when system is idle (by returning > false in idle handler) but since activity never went idle (because it > was that phantom fast Activity) Looper kept my Activity reference - > thus memory leaking. > > but my question remains: what is that phantom Activity which is > created when switching from landscape to portrait? > > thanks > pskink --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
