Am 04.10.2013 08:56, schrieb Paul J Stevens: > Correct. I'm aware of those, but I can't reproduce the leaks myself. I'm > running all kinds of scenarios against imapd running under valgrind: > zero leaks. I've also cleaned up a lot using the coverity scanner. It > found some possible leaks, and they have been cleaned up. > > Most of the coverity work has been done on the master branch though. So > I may have missed a backport to dbmail_3_1, but the same leaks are > probably still present in the master branch as well. Need to rethink > some architectural decisions.
as far as i follow the changelogs the coverity-fixes went only to master maybe some of the few "closing leak" commits in 3.1-tree are coming from there as cherry-pick and not visible in the commit-comment IMHO the coverity scan should go completly over 3.1-tree because it's possible that some of these fixes cover rare situations which are hard to reproduce and there is a chance to get them fixed implicitly trying to reproduce and analyze them which becomes are hard piece of work without knowing how to simulate non-generic load with mixed concurrent clients all having different latency ______________________________________ our machine is running fine with abac5b58c94f270e534320ff264054bc79530b78 while a few days ago it crashed once after a reboot with OOM and 30 minutes later i restarted dbmail-imapd manually because it had again 1300 MB real memory allocated, well that was 2 days ago and now it stays between 180 and 290 MB real memory, so no way to explain the OOM and high-allocation events what i have learned is that some bugs are one visible short after reboot the machine followed by concurrent load, the first spin-lock in august i tried to repdroduce over 10 hours and twice after a reboot of my test-VM it was easy to trigger - finally the same for the OOM, now as the machine is running for a longer time it does not happen again [root@mail:~]$ systemctl status dbmail-imapd.service dbmail-imapd.service - DBMail IMAP Server Loaded: loaded (/usr/lib/systemd/system/dbmail-imapd.service; enabled) Active: active (running) since Mi 2013-10-02 02:03:15 CEST; 2 days ago
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
