Posts tagged grpc.

Cosmos-SDK builds its gRPC server without grpc.MaxConcurrentStreams, so grpc-go defaults to an effectively unbounded stream count and advertises no cap to clients: each held stream pins roughly 7 KB of server state, reaching 7.6 GB RSS at the top of the tested sweep with no plateau in sight.

A pre-auth HTTP/2 stream flood on the rusty-kaspa gRPC P2P endpoint causes inbound-peering exhaustion via eviction and admission denial.

An IOTA node's public gRPC server accepts an unbounded number of concurrent HTTP/2 streams on a single TCP connection, so one client multiplexing around 200 concurrent GetTransactions calls drives resident memory from a few hundred MB to multiple GB in about 10 seconds until the kernel OOM-killer terminates the node.