This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Win2k and cygwin memory leak wrote:

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.


OK then. To sum up. Some people have this problem. There is no known workaround within the context of Cygwin because no one who sees the problem has taken any time or has the ability to debug the problem and look for a workaround/solution within Cygwin, assuming such a thing exists. RAMpage is a reported workaround to this issue for those that see it with Cygwin and/or other Windows apps.

I don't see that further debate on this subject is leading anywhere.
Since the thread has long since turned unproductive, can we end it now?
I'm sure if someone happens to find something useful and relevant, it
will be subsequently reported.


Larry Hall                    
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746

-- Unsubscribe info: Problem reports: Documentation: FAQ:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]