title: rabbitmq+celery memory leak?
body: <p>I have been happily running celery+rabbitmq+django for a month or so in production. Yesterday, I decided to upgrade from celery 2.1.4 to 2.2.4 and now rabbitmq is spinning out of control. After running for a while, my nodes are no longer recognized by evcam, and beam.smp's memory consumptions starts increasing...slowly (100+% CPU usage). </p>
  
  <p>I can run <code>rabbitmqctl list_connections</code> and see that there is nothing unusual (just my one test node). I can see in <code>rabbitmqctl list_queues -p &lt;VHOST&gt;</code> that there are no messages except the heartbeat from my test node. If I let the process keep running over a couple of hours it maxes out the machine.</p>
  
  <p>I've tried purging the various queues using <code>camqadm</code> to no avail and <code>stop_app</code> just hangs. The only way that I have found to 'fix' it is to <code>kill -9</code> beam.smp (and all related processes) and force_reset on my rabbitmq server.</p>
  
  <p>I have no idea how to go about debugging this. There doesn't appear to be anything fishy going on as far as new messages etc. Has anybody run up against this before? Any ideas? What other information should I be looking at?</p>