Java is a safe programming language by providing bytecode verification and enforcing memory protection. For instance, programmers cannot directly access the memory but have to use object references. Yet, the Java runtime provides an Unsafe API as a backdoor for the developers to access the low-level system code. Whereas the Unsafe API is designed to only be used by the Java core library, a growing community of third-party libraries uses it to achieve high performance. The Unsafe API is powerful, but dangerous, which can lead to data corruption, resource leaks, and difficult-to-diagnose JVM crash if used improperly.

In this work, we study the Unsafe crash patterns and propose a memory checker to enforce the memory safety, thus avoiding the JVM crash caused by the misuse of the Unsafe API at the bytecode level. We evaluate our technique on real crash cases from the open JDK bug system and real-world applications from the JVM team of Alibaba. Our tool reduces the efforts from several days to a few minutes for the developers to diagnose the Unsafe related crashes. We also evaluate the runtime overhead of our tool on projects using intensive Unsafe operations, and the result shows that our tool causes a negligible perturbation to the execution of the applications.