I agree; Unless your code creates the threads/thread-pools, i.e. if your
code doesn't own these threads, avoid calling 'setDaemon(...)'.
On Wednesday, February 6, 2013 8:08:47 PM UTC-5, Nathan wrote:
On Wednesday, February 6, 2013 4:52:00 PM UTC-8, Streets Of Boston wrote:
It's mostly
Yeah. In the JVM, your applications owns the process in which it runs.
On Android, the Android framework owns your process and all of the threads
in it. The difference between a thread set daemon and not is pretty much
invisible.
Developers try endless stuff to try to keep their
It's mostly just 'ported' from regular Java, where a process could not do a
normal 'exit' when non-daemon thread were still running.
But you're right. It would seem that if android decides to 'kill' your app,
it doesn't much matter whether there are some daemon threads still running
or not.
On Wednesday, February 6, 2013 4:52:00 PM UTC-8, Streets Of Boston wrote:
It's mostly just 'ported' from regular Java, where a process could not do
a normal 'exit' when non-daemon thread were still running.
But you're right. It would seem that if android decides to 'kill' your
app, it
Great, I think I needed to close a cursor
On May 20, 3:03 pm, fadden fad...@android.com wrote:
On May 19, 9:29 pm, Bob bshumsk...@yahoo.com wrote:
When I debug I get dozens of these exceptions in a row. They don't
seem to effect the program flow but make debugging a nightmare. Does
On May 19, 9:29 pm, Bob bshumsk...@yahoo.com wrote:
When I debug I get dozens of these exceptions in a row. They don't
seem to effect the program flow but make debugging a nightmare. Does
anyone know what is causing this?
Daemon System Thread [5 HeapWorker] (Suspended (exception
There is also an un-official way to do this by reading the /proc filesystem.
I have not seen any official layout documentation of this (you might want to
consult the source code for Android for that), but it seems to be just what
/proc is like on any other Linux system.
So, e.g. getting the all
7 matches
Mail list logo
