From: andrew@pimlott.net (Andrew Pimlott)
Subject: [sup-talk] sup-sync dies; memory limit?
Date: Fri, 8 May 2009 09:42:26 -0700 [thread overview]
Message-ID: <20090508164226.GA28854@pimlott.net> (raw)
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
next reply other threads:[~2009-05-08 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 16:42 Andrew Pimlott [this message]
2009-05-11 18:26 ` Andrew Pimlott
2009-05-12 17:19 ` William Morgan
2009-05-12 18:31 ` Andrew Pimlott
2009-05-12 19:54 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090508164226.GA28854@pimlott.net \
--to=andrew@pimlott.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox