When Capsule Protocol is enabled, the `HttpDatagramHandler` caches the current `RequestDecoder`. During stream recreation, such as an internal redirect, the `ActiveStream` is replaced and the `EnvoyQuicServerStream` is updated, but the handler's cached pointer remains unchanged. Consequently, a subsequent HTTP/3 datagram may trigger the `decodeData()` function using a freed decoder, leading to invalid virtual dispatch and a process crash. This occurs specifically when HTTP/3 datagrams and Capsule Protocol are enabled and the request follows a stream-recreation path.