From: andrew@pimlott.net (Andrew Pimlott)
Subject: [sup-talk] sup-sync dies; memory limit?
Date: Tue, 12 May 2009 11:31:58 -0700 [thread overview]
Message-ID: <20090512183158.GO28854@pimlott.net> (raw)
In-Reply-To: <1242148438-sup-9068@entry>
On Tue, May 12, 2009 at 10:19:48AM -0700, William Morgan wrote:
> Reformatted excerpts from Andrew Pimlott's message of 2009-05-11:
> > On Fri, May 08, 2009 at 09:42:26AM -0700, Andrew Pimlott wrote:
> > > I don't have any memory limits set. Is it possible that sup-sync or
> > > ruby uses some itself? Any other ideas?
>
> Very mysterious.
I cannot reproduce the problem anymore, but as far as I know, nothing
changed on my system (other than the inbox I am testing with evolving
routinely). sup-sync from the 0.7 gem now runs to completion and never
uses more than ~36M virtual memory (before it got up around 60M before
crashing). It doesn't seem possible that the git copy of sup affected
the installed gem. So I'm at a complete loss too.
Andrew
next prev parent reply other threads:[~2009-05-12 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 16:42 Andrew Pimlott
2009-05-11 18:26 ` Andrew Pimlott
2009-05-12 17:19 ` William Morgan
2009-05-12 18:31 ` Andrew Pimlott [this message]
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=20090512183158.GO28854@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