[rabbitmq-discuss] looks like a memory leak, 2.4.1

Matthew Sackman matthew at rabbitmq.com
Thu Apr 28 13:27:34 BST 2011

Hi Mark,

On Wed, Apr 27, 2011 at 05:31:23PM -0600, Mark Geib wrote:
> We have rabbitmq 2.4.1 on debian squeeze, erlang is R14A.

Yes R14A. Which is an unstable beta release of Erlang
(http://www.erlang.org/download_release/7) and should _never_ have been
selected as the version of Erlang for a stable release of Debian. Sigh.

> What we see is that the memory footprint of rabbitmq grows after
> running for just a couple to a few hours. And eventually we get VM
> alarms in the rabbitmq log. The funny thing is that we never queue up
> more a 10-50 messages in any queue, usually in the single digits. So
> the activity seems low, and the queue sizes are small, based on number
> of messages.
> We have seem this with 2.3.1 and then upgraded to 2.4.1 and see the
> same thing.

Hmm, I'd expect some growth due to memory fragmentation but not to the
extent you're suggesting. The connections to the server, they're not SSL
connections are they? Also what is the memory in the server, and have
you left the high watermark at its default 0.4?


More information about the rabbitmq-discuss mailing list