X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Mark Geisert Subject: Re: Memory leakage? Date: Mon, 11 Jun 2007 00:58:59 +0000 (UTC) Lines: 19 Message-ID: References: <20070610115635 DOT M17897 AT edgar-matzinger DOT nl> <011901c7aba8$d2d490f0$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <20070610232043 DOT GA7059 AT ednor DOT casa1 DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Christopher Faylor cygwin.com> writes: On Sun, Jun 10, 2007 at 10:16:41PM +0000, Mark Geisert wrote: > [original question and my incorrect analysis elided...] > > ...and if all Cygwin processes are subsequently exited then it isn't > Cygwin's fault either. Let's not go down this path again. Cygwin has > no magical powers to make Windows permanently use memory. Look to > resident third-party software to perform this feat, not Cygwin. > > cgf Of course you're correct here CGF; sorry for the noise. My home systems and work systems that show the problem have different sets of resident 3rd-party software, none of which seem to be on the Known Bad Apps list. I jumped to the wrong conclusion. The depressing alternate conclusion is that there are more Bad Apps to be added to the list. I'll see if I can figure out what those are. Thanks, ..mark -- 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/