[android-developers] Re: deleteOnExit when and how does an Android JVM exit

2010-04-01 Thread fadden
On Mar 29, 2:20 pm, Streets Of Boston wrote: > In short, don't call System.exit(). :-) Or System.halt(). Or Process.killMeKillMeKillMeNow(). > On Mar 29, 5:10 pm, lordjoe wrote: > > So my take on this is not only can I not COUNT on deleteOnExit() > > behaving properly but I can basically count

[android-developers] Re: deleteOnExit when and how does an Android JVM exit

2010-03-29 Thread Streets Of Boston
Usually, calling System.exit() should not be done. Depending on your manifest settings of your activity, it could be that your activity is loaded into a process of another application. Calling System.exit() will kill the entire application, not just your activity. In short, don't call System.exit(

[android-developers] Re: deleteOnExit when and how does an Android JVM exit

2010-03-29 Thread lordjoe
So my take on this is not only can I not COUNT on deleteOnExit() behaving properly but I can basically count on it never being called. This raises one more question which might need a separate thread - is it ever right for an application to call System.exit(). We are trained not to do this but for

[android-developers] Re: deleteOnExit when and how does an Android JVM exit

2010-03-29 Thread fadden
On Mar 29, 11:33 am, Mark Murphy wrote: > > 2) When does an Application's JVM exit - assuming there is one JVM per > > application. > > That is unclear and definitely varies. For example, the process may be > terminated quickly enough that the JVM does not go through a normal > shutdown procedure.