I filed a bug report (issue 0000462) about this last Wednesday and it hasn't been updated yet. I've noticed a few times where you've responded to list messages telling people to file a report; do you prefer a list email prior to formally reporting a bug?
On Tue, 05 Dec 2006 10:07:26 +0100 Paul J Stevens <[EMAIL PROTECTED]> wrote: > > > Jake Anderson wrote: > > However looking at the memory usage on the "from" > machine the > > dbmail-imapd process starts chewing memory like crazy. > After about 5000 > > messages it reaches the limit of memory and everything > stops. What can I > > do to find the problem? > > Find one of the exact FETCH commands imapsync is using to > get the > messages from the 'from' machine and use it in a valgrind > session to see > where dbmail-imapd is leaking. > > I do this by setting up small txt files like the ones in > test-scripts/testfetch.txt: > > --- > 1 login user pass > 2 select mailbox > 3 uid fetch 12554 ..... # as used by imapsync > 4 logout > --- > > pipe this through a imapd session wrapped in valgrind > where dbmail-imapd > still has the debugging symbols. > > cat testfetch.txt | valgrind --leak-check=full > ./dbmail-imapd -n > > > Or: you can send me the exact fetch command (one or two > will do) so I > can do it for you. > > > -- > ________________________________________________________________ > Paul Stevens paul > at nfg.nl > NET FACILITIES GROUP GPG/PGP: > 1024D/11F8CD31 > The > Netherlands________________________________http://www.nfg.nl > _______________________________________________ > DBmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail >
