The vulnerability description explicitly points to the recvContent function as the source of the flaw, stating that it attempts to optimize performance by pre-allocating memory based on ch.header.Size without validation. The provided commit 91b65fa0096a99a580cf51a31b24028ff1c60382 directly modifies the channel.go file within the recvContent function. The patch shows the addition of logic to cap the headerSize with ch.connection.Config.FrameSize before the make([]byte, 0, headerSize) call. This confirms that the Channel.recvContent function was the exact location where the unbounded memory allocation occurred, making it the vulnerable function. When an attacker sends a message with an excessively large body-size in the content header, this function would be called to process the incoming content, leading to the OOM condition.