Bug#688015: memory leak data update

2012-09-24 Thread Matthias Andree 
Erik,

without either debugging info of a leak detector, or bare necessities to
reproduce the situation per the FAQ
http://www.fetchmail.info/fetchmail-FAQ.html#G3, there is no chance
this can ever be fixed.
(This does not rule out a lucky coincidence, but such a coincidence
might happen in a few years, or never.)

While the memory stats might hint to a leak, more info is required, and
I propose to also provide information from lsof -c fetchmail (run as root).

I will personally also not investigate bugs in 6.3.18, but only in
6.3.22 -- I might be willing to look at bug reports that pinpoint the
location in a code excerpt, however.

It all hinges on a way for me to reproduce the problem, or someone to
send a patch and/or a good explanation how the leak would show up.

Sorry.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#688015: memory leak data update

2012-09-21 Thread Erik Thiele 

hello,

i may update my memory log for reference:

2012-09-17 11,7% VIRT=63852 RES=60316 SHR=1888
2012-09-18 14,6% VIRT=84760 RES=74952 SHR=1884
2012-09-21 22,4% VIRT=117M RES=112M SHR=1892

i'm sorry I will probably not find time right now to do more debugging. 
so meanwhile this bug will just be for reference if other people 
experience the same problem...



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org