From: pierre@baillet.name (Pierre Baillet)
Subject: [sup-talk] memory hog ?
Date: Wed, 10 Oct 2007 10:14:56 +0200 [thread overview]
Message-ID: <6205b42d0710100114i510e3706mfec56d4efe22ab2@mail.gmail.com> (raw)
Hi,
Without touching anything sup now tries to use all the available memory on
my computer and never finishes to start (more than 3GB...). That's a bit
annoying as behaviour. I've not idea on how to solve it, so maybe one of you
has an idea...
Cheers,
--
Pierre Baillet <pierre at baillet.name>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/sup-talk/attachments/20071010/76d85699/attachment.html
next reply other threads:[~2007-10-10 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 8:14 Pierre Baillet [this message]
2007-10-28 3:47 ` 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=6205b42d0710100114i510e3706mfec56d4efe22ab2@mail.gmail.com \
--to=pierre@baillet.name \
/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