When the optional oghttp2 upstream HTTP/2 codec is enabled, the software accepts a response trailer HEADERS frame that lacks an END STREAM flag. This causes the ActiveRequest to be completed and deferred-deleted while the oghttp2 codec maintains the stream as open, resulting in a dangling `response decoder ` reference within ClientStreamImpl. Subsequent frames on the same stream may dispatch through the freed object, leading to a process crash. This issue is specific to the oghttp2 codec, as the default nghttp2 codec rejects these malformed trailers, and the trigger occurs only on the upstream side.