Use visualvm monitoring JVM, I found DestroyJavaVm thread (garbage collector daemon thread) from beginning to end have been running status (wouldn't have been consumed CPU?
This curious on the answer to the following, but didn't solve the question, Since all it is doing is joining all other running threads it does not consume any resources. this sentence is said DestroyJavaVm will join other threads, so will not consume CPU, but join other threads essence is to wait for other threads, so the above visualvm monitoring, DestroyJavaVm should not have a wait state, why all along is running? Great god answer o
https://www.it1352.com/975163.html

=================================================
Complement more DestroyJavaVM under other intellectual (here to search https://www.javatang.com/archives/2017/10/19/51301886.html
"DestroyJavaVM
"
Execute the main () thread after the execution of the call of JNI jni_DestroyJavaVM () method will arouse DestroyJavaVM threads, after JBoss start, will arouse DestroyJavaVM thread, in a wait state, waiting for the other thread (Java thread and native thread) exit notice it uninstall the JVM,

"DestroyJavaVM prio=5" tid=0 x00007fc6b3001000 nid=0 x1903 waiting on condition x0000000000000000 [0]
Java. Lang. Thread. The State: a RUNNABLE