How to Avoid JNI Crashes by Managing Local and Global References Correctly
Most JNI crashes don't come from complicated logic. They come from a small set of mistakes around object references: holding on to a reference after it has become invalid, creating references faster than they're released, or passing a reference to a thread that was never allowed to use it. These bugs are hard to track down because the crash often happens far away from the line that caused it, sometimes minutes later, inside the garbage collector....
Most JNI crashes don't come from complicated logic. They come from a small set of mistakes around object references: holding on to a reference after it has become invalid, creating references faster than they're released, or passing a reference to a thread that was never allowed to use it. These bugs are hard to track down because the crash often happens far away from the line that caused it, sometimes minutes later, inside the garbage collector....