From mboxrd@z Thu Jan  1 00:00:00 1970
From: andrew@pimlott.net (Andrew Pimlott)
Date: Fri, 8 May 2009 09:42:26 -0700
Subject: [sup-talk] sup-sync dies; memory limit?
Message-ID: <20090508164226.GA28854@pimlott.net>

I have been running sup-sync on a new mailbox, and it tends to get
partway through and then die, but not in the same place each time.
Twice, the error has been like

/var/lib/gems/1.8/gems/sup-0.7/lib/sup/crypto.rb:162:in ``': Cannot allocate memory - /usr/bin/gpg --quiet --batch --no-verbose --logger-fd 1 --use-agent --verify /tmp/28751-0-redwood.signature /tmp/28751-0-redwood.payload 2> /dev/null (Errno::ENOMEM)

followed by a backtrace.  Another time, it was just

zsh: killed     /var/lib/gems/1.8/bin/sup-sync --all-sources

I monitored the sup-sync process the last time.  It's memory use grew
slowly, and the process died at around 64M of virtual memory.  I don't
have any memory limits set.  Is it possible that sup-sync or ruby uses
some itself?  Any other ideas?

Andrew