Date: Sun, 15 Jun 2008 19:01:47 -0700 From: James Cook <james.cook@utoronto.ca> To: Tsu-Fan Cheng <tfcheng@gmail.com> Cc: james.cook@utoronto.ca, FreeBSD <freebsd-questions@freebsd.org> Subject: Re: amule eats up my swap!! Message-ID: <20080616020147.GA2810@glider.gateway.2wire.net> In-Reply-To: <f84c38580806130711y22c7421ame4efe5ad00f89c8b@mail.gmail.com> References: <f84c38580806130711y22c7421ame4efe5ad00f89c8b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 13, 2008 at 10:11:02AM -0400, Tsu-Fan Cheng wrote: > Hi all, > I guess this is a rare issue, but "I think" my amule, when no > upload limit, eats up my swap, and cause amule to crash. After I set > limit to 10K, the mule runs fine. I have 1G ram and 2G swap, and > without upload limit, amule crash very often. does anyone know what is > going on?? thank you! I've had problems with aMule crashing too. Typically it would run fine for a few hours, and then it would suddenly start allocating memory (my system memory usage graph went from a flat line to a line climbing with constant slope) and then it would exit and leave a core file behind. It might have been a segfault, but I don't remember. I'm not able to test it right now. My solution at the time was to run amule with "while true; do amule; done". James
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080616020147.GA2810>