On Thu, Jun 7, 2012 at 7:29 AM, Daniel Drozdzewski <
daniel.drozdzew...@gmail.com> wrote:
> Setting launchMode to 'singleInstance' can solve this 'issue', as it
> will force each (re)created activity to launch in a separate task.
>
OMG, do NOT use "singleInstance" to "solve" the problem. This is
RIght, the activity instance tracker depends on GC to decrement its value.
https://github.com/android/platform_frameworks_base/blob/master/core/java/android/app/Activity.java#L732
https://github.com/android/platform_frameworks_base/blob/master/core/java/android/os/StrictMode.java#L2149
Using onD
On 7 June 2012 15:06, Kostya Vasilyev wrote:
> I remember seeing this in one of my apps in certain cases.
>
> My conclusion was that this might be a bug in strict mode code, and disabled
> it.
>
> Activity orientation changes are processed within a single message loop
> heartbeat, so it's entirely
I remember seeing this in one of my apps in certain cases.
My conclusion was that this might be a bug in strict mode code, and
disabled it.
Activity orientation changes are processed within a single message loop
heartbeat, so it's entirely possible that the lifecycles of both activity
instances o
4 matches
Mail list logo