Netty HTTP/2 decompression direct-memory leak crashes JVMs over long-lived connections
Netty's DelegatingDecompressorFrameListener retains a ByteBuf on every HTTP/2 DATA frame but fails to release it when the decompressor channel is already closed. A remote unauthenticated peer can leak one direct ByteBuf per DATA frame across a long-lived HTTP/2 connection, exhausting direct memory and crashing the JVM with OutOfMemoryError.
Any Java service exposing HTTP/2 with content-encoding decompression enabled (common in gRPC gateways and Spring WebFlux) should pull the patched Netty. If you can't upgrade this week, disabling automatic HTTP/2 decompression is the workaround.