Java 25 + grpc-netty-shaded 1.78.0 appearance warning

[xermaor]

WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::allocateMemory has been called by io.grpc.netty.shaded.io.netty.util.internal.PlatformDependent0$2 (file:/Users/linsihan/.gradle/caches/modules-2/files-2.1/io.grpc/grpc-netty-shaded/1.78.0/ab48302cc37050ef6f0c2a3f12ebaf4b94e4c6f1/grpc-netty-shaded-1.78.0.jar)
WARNING: Please consider reporting this to the maintainers of class io.grpc.netty.shaded.io.netty.util.internal.PlatformDependent0$2
WARNING: sun.misc.Unsafe::allocateMemory will be removed in a future release

[kannanjgithub]

Netty 4.2 removes the deprecated method usage in sun.misc.Unsafe, so when grpc-netty-shaded upgrades to use Netty 4.2, it will be automatically fixed.

[btbouwens]

Netty 4.2 removes the deprecated method usage in sun.misc.Unsafe, so when grpc-netty-shaded upgrades to use Netty 4.2, it will be automatically fixed.

Sounds like a solution, but this hasn't happened yet? So it isn't fixed yet.

[btbouwens]

I made a netty-4.2 branch here: https://github.com/btbouwens/grpc-java
Indeed the above warning goes away.
There are still Warnings about terminally deprecated Unsafe due to protobuf though, see
protocolbuffers/protobuf#20760

[RECHERGG]

Hi, is there any update on this?

I’ve been waiting for a while now and expected this to be fixed with a newer release, but I’m still seeing the warning on recent versions.

Has the upgrade to Netty 4.2 (or any other fix) already happened, or is this still pending?

[btbouwens]

If I see this correctly, Netty was just updated to 4.1.132, and this ticket requires 4.2.

[RECHERGG]

Is there any ETA for upgrading to Netty 4.2?

[kannanjgithub]

Before upgrading to Netty 4.2 we would need to verify internally at Google if our prod systems are able to work with Netty 4.2 without problems or not. Some testing is already underway, and the results of that will indicate to us how soon we can do the upgrade to Netty 4.2. We don't have an ETA yet.

[RECHERGG]

Before upgrading to Netty 4.2 we would need to verify internally at Google if our prod systems are able to work with Netty 4.2 without problems or not. Some testing is already underway, and the results of that will indicate to us how soon we can do the upgrade to Netty 4.2. We don't have an ETA yet.

Thanks for the update, appreciate the clarification.

Totally understand that this needs proper internal testing first. From a user perspective in our terminal application the warning is a bit annoying though, since it shows up regularly.

I’ll keep an eye on this issue, would be great to get an update once there’s any progress 👍

[michaelkoepf]

hi @kannanjgithub and others.

is this fixed in v1.83.0? From the release notes:

Upgrade to Netty 4.2.15 (66c6ab1). If you need Netty 4.1 support, please file an issue

[kannanjgithub]

Yes, it should be fixed now.