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 Sensitivity: Subject: Re: Win2k and cygwin memory leak To: cygwin AT cygwin DOT com From: Brian DOT Kelly AT empireblue DOT com Date: Fri, 8 Aug 2003 09:32:16 -0400 Message-ID: MIME-Version: 1.0 X-WSS-ID: 132D7966456284-01-03 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Note-from-DJ: This may be spam > Looking at RAMpage's code and reading the description, I see nothing > that indicates it would solve this supposed "memory leak" problem. All > that it does is allocate a huge chunk of memory and free it, forcing any > fragmented memory out onto disk. I really don't see how that would > cause any improvement in anything related to a memory leak. I do not know much, but I do know this. With RAMpage running 4 times a day, my server stays up. Without it, it crashes. The only thing running on the box other than the naked OS and backup software and Anti-virus, is cygwin and cygwin installed apps. I agree with you to the extent that it certainly doesn't *solve* the *supposed* memory leak problem. But it keeps my server up and I'm sure it will help others too. BK "Christopher Faylor" @cygwin.com on 08/07/2003 10:48:57 PM Please respond to cygwin AT cygwin DOT com Sent by: cygwin-owner AT cygwin DOT com To: cygwin AT cygwin DOT com cc: (bcc: Brian Kelly/WTC1/Empire) Subject: Re: Win2k and cygwin memory leak On Fri, Aug 08, 2003 at 03:44:11AM +0200, Luc Hermitte wrote: >* On Thu, Aug 07, 2003 at 03:24:26PM -0700, Andrew DeFaria wrote: >>It has already been acknowledged several times over that it is not a >>problem of Cygwin's rather a problem of Windows. > >I think we all agree to that. But unfortunatelly, so far, only Cygwin >seems affected by that problem. You're referencing facts not in evidence. We don't know that it is only Cygwin. I haven't seen any evidence that anyone has done any research on this. We don't know that this isn't triggered by something as simple as a virus checker. >> When you cluelessly continue to assert that it's a Cygwin memory leak >> is exactly where is leads down the path to character assassinations. > >Could we say that cygwin relies on a faulty library developped by >Microsoft ? And that nobody has identified the faulty library ? Saying this would be pure speculation. Just as an observation: I went to the RAMpage home page and, curiously, it does not prominently mention cygwin. In fact, I couldn't find a mention of cygwin at all. If this was a problem that only manifested with cygwin programs, I would think that RAMpage would mention that fact. Looking at RAMpage's code and reading the description, I see nothing that indicates it would solve this supposed "memory leak" problem. All that it does is allocate a huge chunk of memory and free it, forcing any fragmented memory out onto disk. I really don't see how that would cause any improvement in anything related to a memory leak. cgf -- 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/ "WellChoice, Inc." made the following annotations on 08/08/2003 09:34:38 AM ------------------------------------------------------------------------------ Attention! This electronic message contains information that may be legally confidential and/or privileged. The information is intended solely for the individual or entity named above and access by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Release/Disclosure Statement -- 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/