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

---------------------- Forwarded by Brian Kelly/WTC1/Empire on 08/07/2003
10:07 PM ---------------------------

Brian Kelly
08/07/2003 10:06 PM

To:    "Luc Hermitte" <>

Subject:    Re: Win2k and cygwin memory leak  (Document link: Brian Kelly)

*You're Welcome*

For it *I* the *clueless* (cfg's pet name for me) one who has brought the
gift of RAMpage to the cygwin world.
(Many thanks to J. Fitz who wrote it!).

I will post in a couple of days a perl script that you can then use with
cron and RAMpage that
will enable you to use Cygwin "reboot free".

As it "ought" to be.

Brian Kelly

"Luc Hermitte" <> on 08/07/2003 09:44:11 PM

Sent by:

cc:     (bcc: Brian Kelly/WTC1/Empire)

Subject:    Re: Win2k and cygwin memory leak

* 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.
Hence, every now and then, the question will be asked on this list.
Because this is an extremly annoying bug that we have very little chance
to run into if we are not using Cygwin.

I guess cygwin is using a library not always correctly implemented.
"Isn't there any workaround cygwin could use ? " is a typical question
for many of us.

> What else do you want?

Personnally, I hope, as the question will be raised again and again,
that an expertise will emerge. Just knowing why there is a problem will
be a big step ahead -- ie: which library/service pack/... is faulty.

This time, someone told us about a freeware that collects "forgotten"
memory. Many thanks to him! If, thanks to this program, I will be able
to run ./configure for mutt or run my computer for more than 2 days (or
2 hours) without the need to reboot ... you have no idea of how glad I
will be.

That kind of answer is want we expect. That is not a definitive bug fix,
but a possible workaround.

BTW, if this program is an effective workaround, I think this will merit
a topic in the FAQ.

> 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 ?

Luc Hermitte
PS: don't mistake me, Cygwin is a wonderful project. And I thank people
like Christopher who work so hard on it.

Unsubscribe info:
Problem reports:

"WellChoice, Inc." made the following
 annotations on 08/07/2003 10:09:35 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:
Problem reports:

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