It is not a bug in the JVM, it is an obscure bug in the JNI-ed code. As to why this happens - perhaps read the blog post?