Summary
-------


Issue a warning at run time on the first occasion that any memory-access method in `sun.misc.Unsafe` is invoked. All of these unsupported methods were terminally deprecated in JDK 23. They have been superseded by standard APIs, namely the VarHandle API ([JEP 193](https://openjdk.org/jeps/193), JDK 9) and the Foreign Function & Memory API ([JEP 454](https://openjdk.org/jeps/454), JDK 22). We strongly encourage library developers to migrate from `sun.misc.Unsafe` to supported replacements, so that applications can migrate smoothly to modern JDK releases.


History
-------

This JEP is the successor of [JEP 471](https://openjdk.org/jeps/471) (JDK 23), which deprecated the memory-access methods in `sun.misc.Unsafe` for removal in a future release and described a gradual process of removal. The Goals, Non-Goals, Motivation, and Risks and Assumptions sections of this JEP are essentially identical to that of JEP 471.


## Goals

- Prepare the ecosystem for the removal of the memory-access methods in `sun.misc.Unsafe` in a future JDK release.

- Notify developers when their applications use, directly or indirectly, the memory-access methods in `sun.misc.Unsafe`.


## Non-Goals

- It is not a goal to issue warnings upon use of any member of the `sun.misc.Unsafe` class. A small number of its methods are not used for memory access; these will be deprecated and removed separately.


## Motivation

The `sun.misc.Unsafe` class was introduced in 2002 as a way for Java classes in the JDK to perform low-level operations. Most of its methods — 79 out of 87 — are for accessing memory, either in the JVM's garbage-collected heap or in off-heap memory, which is not controlled by the JVM. As the name of the class suggests, these memory-access methods are unsafe: They can lead to undefined behavior, including JVM crashes. Therefore, they were not exposed as a standard API. They were neither envisaged for use by a broad range of clients nor intended to be permanent. Rather, they were introduced with the assumption that they were exclusively for use within the JDK, and that callers within the JDK would perform exhaustive safety checks before using them, and that safe standard APIs for this functionality would eventually be added to the Java Platform.

However, with no way in 2002 to prevent `sun.misc.Unsafe` from being used outside the JDK, its memory-access methods became a handy tool for library developers who wanted more power and performance than standard APIs could offer. For example, `sun.misc.Unsafe::compareAndSwap` can perform a CAS (compare-and-swap) operation on a field without the overhead of the `java.util.concurrent.atomic` API, while `sun.misc.Unsafe::setMemory` can manipulate off-heap memory without the 2GB limitation of [`java.nio.ByteBuffer`](https://docs.oracle.com/en/java/javase/22/docs/api/java.base/java/nio/ByteBuffer.html). Libraries that do rely on `ByteBuffer` to manipulate off-heap memory, such as Apache Hadoop and Cassandra, use `sun.misc.Unsafe::invokeCleaner` to improve efficiency by deallocating off-heap memory promptly.

Unfortunately, not all libraries are diligent at performing safety checks before calling the memory-access methods, so there is a risk of failures and crashes in applications. Some uses of the methods are unnecessary, driven by the ease of copy-and-paste from online forums. Other uses of the methods may cause the JVM to disable optimizations, resulting in worse performance than if ordinary Java arrays had been used. Nevertheless, because use of the memory-access methods is so widespread, `sun.misc.Unsafe` was not encapsulated alongside other low-level APIs in JDK 9 ([JEP 260](https://openjdk.org/jeps/260)). It remains available out-of-the-box in JDK 23, pending the availability of safe supported alternatives.

Over the past several years, we have introduced two standard APIs that are safe and performant replacements for the memory-access methods in `sun.misc.Unsafe`:

- [`java.lang.invoke.VarHandle`](https://docs.oracle.com/en/java/javase/22/docs/api/java.base/java/lang/invoke/VarHandle.html), introduced in JDK 9 ([JEP 193](https://openjdk.org/jeps/193)), provides methods to safely and efficiently manipulate on-heap memory, i.e., fields of objects, static fields of classes, and elements of arrays.

- [`java.lang.foreign.MemorySegment`](https://docs.oracle.com/en/java/javase/22/docs/api/java.base/java/lang/foreign/MemorySegment.html), introduced in JDK 22 ([JEP 454](https://openjdk.org/jeps/454)), provides methods to safely and efficiently access off-heap memory, sometimes in cooperation with `VarHandle`.

These standard APIs guarantee no undefined behavior, promise long-term stability, and have high-quality integration with the tooling and documentation of the Java Platform. (Examples of their use are given in [JEP 471](https://openjdk.org/jeps/471#Migration-examples).) Given the availability of these APIs, it is now appropriate to deprecate and eventually remove the memory-access methods in `sun.misc.Unsafe`.

Removing the memory-access methods in `sun.misc.Unsafe` is part of a long-term coordinated effort to ensure that the Java Platform has [integrity by default](https://openjdk.org/jeps/8305968). Other initiatives include placing restrictions on the Java Native Interface (JNI, [JEP 472](https://openjdk.org/jeps/8307341)) and on the dynamic loading of agents ([JEP 451](https://openjdk.org/jeps/451)). These efforts will make the Java Platform more secure and more performant. They will also reduce the risk of application developers becoming trapped on older JDK releases due to libraries that break on newer releases when unsupported APIs are changed.


## Description

We are deprecating and removing the memory-access methods in `sun.misc.Unsafe` in phases:

1. JDK 23 [deprecated all of the memory-access methods for removal](https://openjdk.org/jeps/471). This caused compile-time deprecation warnings for code that refers to the methods, alerting library developers to their forthcoming removal.

2. <a name="phase-2"/> JDK 24 will, by default, issue a warning on the first occasion that any memory-access method is used, whether directly or via reflection. That is, it will issue at most one warning regardless of which memory-access methods are used and how many times any particular method is used. This will alert application developers and users to the forthcoming removal of the methods, and the need to upgrade libraries. An example of the warning is:

    ```
    WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
    WARNING: sun.misc.Unsafe::setMemory has been called by com.foo.bar.Server (file:/tmp/foobarserver/thing.jar)
    WARNING: Please consider reporting this to the maintainers of com.foo.bar.Server
    WARNING: sun.misc.Unsafe::setMemory will be removed in a future release
    ```

3. JDK 26 or later will throw an exception whenever a memory-access method is used, whether directly or via reflection. This will further alert application developers and users to the imminent removal of the methods.

4. In releases after JDK 26, we will remove memory-access methods which have had standard replacements since JDK&nbsp;9 (2017).

5. In releases after JDK 26, we will remove memory-access methods which have only had standard replacements since JDK&nbsp;22 (2023).

A complete list of the memory-access methods and their standard replacements can be found in [JEP&nbsp;471](https://openjdk.org/jeps/471#sun-misc-Unsafe-memory-access-methods-and-their-replacements).


### Identifying uses of the memory-access methods in `sun.misc.Unsafe`

The vast majority of Java developers do not use `sun.misc.Unsafe` explicitly in their own code. However, many applications depend, directly or indirectly, on libraries that use the memory-access methods in `sun.misc.Unsafe`.

In JDK&nbsp;23 and later, you can assess how libraries that you use are affected by the deprecation and removal of these methods by running with a new command line option, `--sun-misc-unsafe-memory-access={allow|warn|debug|deny}`. This option is similar, in spirit and in form, to the `--illegal-access` option introduced by [JEP&nbsp;261](https://openjdk.org/jeps/261#Relaxed-strong-encapsulation) in JDK&nbsp;9. It works as follows:

- `--sun-misc-unsafe-memory-access=allow` allows use of the memory-access methods with no warnings at run time.

  This mode was the default in JDK 23.

- `--sun-misc-unsafe-memory-access=warn` allows use of the memory-access methods, but issues a single warning as described [above](#phase-2).

  This mode will be the default in JDK 24.

- `--sun-misc-unsafe-memory-access=debug` allows use of the memory-access methods, but issues a one-line warning and a stack trace on every occasion that any memory-access method is used, whether directly or via reflection.

- `--sun-misc-unsafe-memory-access=deny` disallows use of the memory-access methods by throwing an `UnsupportedOperationException` on every occasion that any such method is used, whether directly or via reflection.

The default value of the `--sun-misc-unsafe-memory-access` option changes from release to release as we proceed through the phases described above:

- `allow` was the default value in phase 1 (JDK 23).

- `warn` will be the default value in phase 2 (JDK 24), as if every invocation of the `java` launcher includes `--sun-misc-unsafe-memory-access=warn`. It is possible to revert the value from `warn` to `allow` in JDK&nbsp;24, thus avoiding the warning. That is, the `java` launcher can be invoked with `--sun-misc-unsafe-memory-access=allow`.

- `deny` will be the default value in phase 3 (JDK&nbsp;26 or later). It will be possible in phase 3 to revert the value from `deny` to `warn` in order to receive a single warning rather than exceptions. It will not be possible to use `allow` to avoid the warning.

- In phase 5, when all of the memory-access methods have been removed, `--sun-misc-unsafe-memory-access` will be ignored. Eventually it will be removed.

You can also use JDK Flight Recorder (JFR) to identify when memory-access methods are used. When JFR is enabled on the command line, the JVM records a `jdk.DeprecatedInvocation` event whenever a terminally deprecated method is invoked. This event can be used to identify uses of the memory-access methods in `sun.misc.Unsafe`. For example, here is how to create a JFR recording and then display the `jdk.DeprecatedInvocation` events:

```
$ java -XX:StartFlightRecording:filename=recording.jfr ...
$ jfr print --events jdk.DeprecatedInvocation recording.jfr
jdk.DeprecatedInvocation {
  startTime = 11:53:00.196 (2024-11-08)
  method = sun.misc.Unsafe.staticFieldOffset(Field)
  invocationTime = 11:53:00.174 (2024-11-08)
  forRemoval = true
  stackTrace = [
    Foo.main(String[]) line: 16
    ...
  ]
}
$ 
```

Further details on this event and its limitations can be found in the [JDK&nbsp;22 release note](https://www.oracle.com/java/technologies/javase/22-relnote-issues.html#JDK-8211238).


## Risks and Assumptions

- Over the years, methods in `sun.misc.Unsafe` that are unrelated to memory access have been deprecated for removal after standard replacements were introduced, and many of them have already been removed:

  - `sun.misc.Unsafe::defineClass` was [removed in JDK&nbsp;11](https://bugs.openjdk.org/browse/JDK-8199699) after [`java.lang.invoke.MethodHandles.Lookup::defineClass`](https://docs.oracle.com/en/java/javase/22/docs/api/java.base/java/lang/invoke/MethodHandles.Lookup.html#defineClass(byte[])) was introduced in JDK&nbsp;9.

  - `sun.misc.Unsafe::defineAnonymousClass` was [removed in JDK&nbsp;17](https://bugs.openjdk.org/browse/JDK-8266760) after [`MethodHandles.Lookup::defineHiddenClass`](https://docs.oracle.com/en/java/javase/22/docs/api/java.base/java/lang/invoke/MethodHandles.Lookup.html#defineHiddenClass(byte[],boolean,java.lang.invoke.MethodHandles.Lookup.ClassOption...)) was introduced in [in JDK&nbsp;15](https://openjdk.org/jeps/371).

  - `sun.misc.Unsafe::{ensureClass,shouldBe}Initialized` were [removed in JDK&nbsp;22](https://bugs.openjdk.org/browse/JDK-8316284) after [`MethodHandles.Lookup::ensureInitialized`](https://docs.oracle.com/en/java/javase/22/docs/api/java.base/java/lang/invoke/MethodHandles.Lookup.html#ensureInitialized(java.lang.Class)) was introduced in JDK&nbsp;15.

  - Six miscellaneous methods in `sun.misc.Unsafe` were [deprecated for removal in JDK&nbsp;22](https://bugs.openjdk.org/browse/JDK-8315953) after standard replacements were available.

  We have seen very little impact in the Java ecosystem from the removal of these relatively obscure methods. However, the memory-access methods are much better known. This proposal assumes that removing them will impact libraries. Accordingly, for maximum visibility, we are proposing their deprecation and removal via the JEP process rather than simply with a CSR request and a release note.

- This proposal assumes that library developers will migrate from unsupported methods in `sun.misc.Unsafe` to supported methods in `java.*`.

  > **We recommend in the strongest possible terms that library developers do not migrate from unsupported methods in `sun.misc.Unsafe` to unsupported methods found elsewhere inside the JDK.**

  Library developers who ignore this recommendation will force their users to run with `--add-exports` or `--add-opens` options on the command line. This is not merely inconvenient, but risky: JDK internals can change from release to release without notice, breaking libraries which depend on the internals, thereby breaking applications which depend on the libraries.

- A risk of this proposal is that some libraries use the on-heap memory-access methods of `sun.misc.Unsafe` in ways that cannot be replicated by the standard APIs available in JDK&nbsp;23. For example, a library may use `Unsafe::objectFieldOffset` to obtain the offset of a field in an object, then use `Unsafe::putInt` to write an `int` value at that offset regardless of whether the field is an `int`. The standard `VarHandle` API cannot examine or manipulate objects at such a low level because it refers to fields by name and type, not by offset.

  Use cases that rely on field offsets are, in effect, revealing or exploiting implementation details of the JVM. In our view, such use cases do not need to be supported by a standard API.

- A library may use `UNSAFE.getInt(array, arrayBase + offset)` to access array elements in the heap without bounds checking. This idiom is typically used for random access, since sequential access to array elements, whether via ordinary array-index operations or the `MemorySegment` API, already benefits from the JIT's bounds-check elimination.

  In our view, random access to array elements without bounds checking is not a use case that needs to be supported by a standard API. Random access via array-index operations or the `MemorySegment` API has a small loss of performance compared to the on-heap memory access methods of `sun.misc.Unsafe`, but a large gain in safety and maintainability. In particular, the use of standard APIs is guaranteed to work reliably on all platforms and all JDK releases, even if the JVM's implementation of arrays changes in the future.