umm.. i don't think so - process was still there in the tasks list
On Mar 6, 2:22 pm, Marco Nelissen <[email protected]> wrote:
> It's not so much that your object got GC'd, but that your process was
> removed because nothing was running in it, and space was needed for
> other processes.
> If you want something to run in the background, use a service.
> If you just need to store some properties between invocations of your
> app, write them to a SharedPreference or something, don't keep an
> entire process around to hold them.
>
> On Fri, Mar 6, 2009 at 11:59 AM, Alexey <[email protected]> wrote:
>
> > Hi All , i have a config class where i store properties . It has a
> >staticreference to itself and I initialize it when i start the
> > application. But if i'm if i switch back to my app after like an hour
> > of initial run - it looks like this object gets GC and not exist
> > anymore. As a workaround i start to check for it at onStart in my
> > activities but still don't understand why it's gone if it has astatic
> > reference.
>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
