On 19 nov 2005, at 10:41, Steve Langasek wrote:
Do we actually have reason to believe that this is a memory leak,
i.e., leaving the daemon running will continue to eat more memory? If
the program simply needs 70-some MB to run, that's unfortunate
Well, if a simple IRC proxy would require tha
Hello,
Do we actually have reason to believe that this is a memory leak, i.e.,
leaving the daemon running will continue to eat more memory? If the program
simply needs 70-some MB to run, that's unfortunate, but not RC; if, OTOH,
its memory usage continues to grow beyond the point shown in the bug
Oops, didn't set up GMail yet to forward BTS mails too, so I missed
this one for a while...
On 13/10/05, Frans Pop <[EMAIL PROTECTED]> wrote:
> After running ctrlproxy for a fairly long time as daemon:
> Mem: 30180 29248932 0 1336 5596
> -/+ buffers/cache:
On Mon, 24 Oct 2005 18:46:13 +0300, Faidon Liambotis <[EMAIL PROTECTED]>
writes:
> upstream's SVN log shows several bugfixes, including memory leak
> fixes. An update to the latest version will probably fix these
> problems.
Actually, Debian already contains the most recent upstream release,
2.6.2
On Monday 24 October 2005 17:46, Faidon Liambotis wrote:
> Moreover, I highly doubt that memory leak bugs are justified as
> severity "critical".
For regular applications I would agree. For an application that runs as a
daemon and is likely to run permanently on a server, I think an RC
severity
upstream's SVN log shows several bugfixes, including memory leak fixes.
An update to the latest version will probably fix these problems.
Moreover, I highly doubt that memory leak bugs are justified as severity
"critical".
This looks as severity inflation to me, but I'll leave the maintainer to
ju
Package: ctrlproxy
Version: 2.6.2-1
Severity: critical
Justification: breaks unrelated software
After running ctrlproxy for a fairly long time as daemon:
Mem: 30180 29248932 0 1336 5596
-/+ buffers/cache: 22316 7864
Swap:60440 60440
7 matches
Mail list logo
