Mail Archives: cygwin/2003/08/07/13:00:14
Forgot to add that I call the perl script every *FIVE* minutes - 24-7. The
script is VERY memory intensive
so it really works cygwin and the 2000 Server HEAVY. If I didn't scrub the
memory four times a day, the box
would crash - and did just recently when I had turned off RAMpage for
testing.
Brian Kelly
Brian DOT Kelly AT empireblue DOT com@cygwin.com on 08/07/2003 12:52:53 PM
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
Now seems to be a good time for me to jump in.
I can DEFINITIVELY say that *something* within cygwin - or perl (using
Cygwin's perl) - causes a very real and very measurable
memory leak. I run a 24-7 automated FTP encryption architechture using
cygwin cron which launches a perl
script that automates telnet and ftp from the inetutils package. After each
invocation, memory is lost. The only
thing that keeps the box from dying completely is that in the very same
crontab I call - four times a day - a
memory manager called *RAMpage* which is also open source and can be
invoked from the command line.
This program frees up the lost memory allowing me to essentially run the
server indefinitely. I would of course rather
not have to use RAMpage at all - but since there's ongoing denial about the
existence of "memory leaks" *somewhere* in
the vastness of cygwin - I have no choice but to resort to that which
*works*. Ah well, someday the denial will end, or the
problem will get fixed unintentionally when some other change is made and
the "cygworld will go on". In the meantime,
I have a solution - kludgy you can be sure - but it works and has been
doing so for nearly nine months.
RAMpage => http://www.jfitz.com/software/RAMpage/
Brian Kelly
"Christopher Faylor" <cgf-idd AT cygwin DOT com>@cygwin.com on 08/07/2003 11:40:57
AM
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 Thu, Aug 07, 2003 at 11:32:42AM -0400, Rolf Campbell wrote:
>This may be a Win2000 problem, not a cygwin problem...What service pack
>are you running?
"May be"? You run a bunch of programs, exit them, and Windows slowly loses
memory after each exit?
Hard to see how that's a cygwin problem.
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/07/2003 12:55:14 PM
------------------------------------------------------------------------------
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/
"WellChoice, Inc." made the following
annotations on 08/07/2003 01:02:16 PM
------------------------------------------------------------------------------
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/
- Raw text -