By Peter Lawrey
sun.misc.Unsafe has been in Java from at least as far back as Java 1.4 (2004). In Java 9, Unsafe will be hidden along with many other, for-internal-use classes. to improve the maintainability of the JVM. While it is still unclear exactly what will replace Unsafe, and I suspect it will be more than one thing which replaces it, it raises the question, why is it used at all?
Doing things which the Java language doesn’t allow but are still useful.
Java doesn’t allow many of the tricks which are available to lower level languages. For most developers this is very good thing, and it not only saves you from yourself, it also saves you from your co-workers. It also makes it easier to import open source code because you know there is limits to how much damage they can do. Or at least there is limits to how much you can do accidentally. If you try hard enough you can still do damage.
But why would you even try, you might wonder? When building libraries many (but not all) of the methods in Unsafe are useful and in some cases, there is no other way to do the same thing without using JNI, which is even more dangerous and you lose the “compile once, run anywhere”
Deserialization of objects
When deserializing or building an object using a framework, you make the assumption you want to reconstitute an object which existed before. You expect that you will use reflection to either call the setters of the class, or more likely set the internal fields directly, even the final fields. The problem is you want to create an instance of an object, but you don’t really need a constructor as this is likely to only make things more difficult and have side effects.
In this class, you should be able to rebuild and set the final field, but if you have to call a constructor and it might do things which don’t have anything to do with deserialization. For these reasons many libraries use Unsafe to create instances without calling a constructor
Calling allocateInstance avoids the need to call the appropriate constructor, when we don’t need one.
Thread safe access to direct memory
Another use for Unsafe is thread safe access to off heap memory. ByteBuffer gives you safe access to off heap or direct memory, however it doesn’t have any thread safe operations. This is particularly useful if you want to share data between processes.
When you run this in two programs, one with odd and the other with even. You can see that each process is changing data via persisted shared memory.
In each program it maps the same are of the disks cache into the process. There is actually only one copy of the file in memory. This means the memory can be shared, provided you use thread safe operations such as the volatile and CAS operations.
The output on an i7-3970X is
Waiting for the other odd/even
… Finished, average ping/pong took 83 ns
That is 83 ns round trip time between two processes. When you consider System V IPC takes around 2,500 ns and IPC volatile instead of persisted, that is pretty quick.
Is using Unsafe suitable for work?
I wouldn’t recommend you use Unsafe directly. It requires far more testing than natural Java development. For this reason I suggest you use a library where it’s usage has been tested already. If you wan to use Unsafe yourself, I suggest you thoughly test it’s usage in a stand alone library. This limits how Unsafe is used in your application and give syou a safer, Unsafe.
It is interesting that Unsafe exists in Java, and you might to play with it at home. It has some work applications especially in writing low level libraries, but in general it is better to use a library which uses Unsafe which has been tested than use it directly yourself.