Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 30 Jan 2004 18:43:47 +0600 From: Mike Jastrebtsoff Reply-To: Mike Jastrebtsoff Message-ID: <245902169.20040130184347@pisem.net> To: cygwin AT cygwin DOT com Subject: Re[2]: memory leaks in fork(?) In-Reply-To: <20040130103225.GE3076@jade> References: <1756718839 DOT 20040130162520 AT pisem DOT net> <20040130103225 DOT GE3076 AT jade> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Hello, Luc. Yep! You were completely right. I removed Agnitum Outpost and my build process began to work. I wonder why stopping of Outpost sevice doesn't work out - only total delete. Evidently outpost has resident driver(TCP packet filter?) which causes this troubles with memory leaks. I emailed to Agnitum support service and informed them about this issue. Thank you very much! P.S. But I was shocked with MS XP complexity - common programs can have dependencies with low-level driver! -- With best regards, Mike LH> If you are using Agnitum Outpost Firewall ... try uninstall it a use LH> another firewall. LH> On this new machine, (where XP has been reinstalled from scratch), I'm LH> no longer using AOF, but Kerio. Since then, I don't need to reboot every LH> two days or every half-make-configure. LH> So far, the hyppothesis of a ressource leak in AOF seems accurate. LH> HTH. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/