DestroyJavaVM thread ALWAYS running
This happens because most applications are run in threads.
All POJO apps start by invoking the main
method. In its most simple case, this method will do all of the work, creating objects, calling methods etc. Once main
completes, the JVM is told to shut down using a DestroyJavaVM
thread which waits for all non-daemon threads to complete before doing its work. This is to ensure that any non-daemon threads you create run to completion before the JVM is torn down.
An app with a GUI, however, normally runs as a number of threads. One for watching for system events such as keyboard or mouse events. One for maintaining the windows and display etc. The main
method of this kind of app will probably just start up all the required threads and exit. It still creates the DestroyJavaVM
thread but now all that it does is wait for all of your created threads to finish before tearing down the VM.
As a result, any app that creates threads and relies solely on their functionality will always have a DestroyJavaVM
thread waiting for it to finish. Since all it is doing is join
ing all other running threads it does not consume any resources.
This barely scratches the surface. It helps to recognize that there are System-triggered Quits and ForceQuits, and the app must know how to respondwithout being blocked indefinitely by non-daemen threads.
As a Java programmer, I need to know when the OS is telling the app to close down (so I can save the User's Work).