The taken memory is never
freed until os restart.
I don’t think Cygwin could do that even if it wanted to, given that you
don’t have any Cygwin services running. Once the last Cygwin process
dies, the OS *will* release the memory it was holding.
It does, however, seem vulnerable to fork
Running the following lines let windows physical memory grow until no
more left (task-manager: physical memory). The taken memory is never
freed until os restart. This happens also while compiling huge
projects. Tested on three different Windows 7 x64 machines with actual
cygwin 2.x (32 and 64
On Jun 11, 2015, at 2:06 PM, Frank Morauf fr...@morauf.de wrote:
Running the following lines let windows physical memory grow until no
more left (task-manager: physical memory).
I’ve run it here in two separate sessions of about 10 minutes each. Memory
usage isn’t growing. Windows 10
Hi, I encountered memory leaks problems compiling a large code under cygwin.
I tried both under winxp and win2k with same result: the memory resources of
the system started slowly falling down, up to the end of the process with
error messages like fork: resource temporarily unavailable.
I found
Luca Trevisani wrote:
Hi, I encountered memory leaks problems compiling a large code under
cygwin.
I tried both under winxp and win2k with same result: the memory
resources of
the system started slowly falling down, up to the end of the process with
error messages like fork: resource
On Tue, Aug 12, 2003 at 10:31:19AM +0300, Nedko Arnaudov wrote:
This is the proof.
http://www.faultcentral.org/personal/nedko/soft/pootag.JPG
http://www.faultcentral.org/personal/nedko/soft/taskmanager.JPG
These are two jpeg images with no words describing what we are supposed
to be looking at.
On Sun, 17 Aug 2003, Christopher Faylor wrote:
On Tue, Aug 12, 2003 at 10:31:19AM +0300, Nedko Arnaudov wrote:
This is the proof.
http://www.faultcentral.org/personal/nedko/soft/pootag.JPG
I think that he is trying to point out that the SeOn kernel memory pool
occupies about 120 MB of
]
To:[EMAIL PROTECTED]
cc: (bcc: Brian Kelly/WTC1/Empire)
Subject:Re: Win2k and cygwin memory leak
[EMAIL PROTECTED] wrote:
Gosh, isn't there a *win* in *cygwin*?? Not that I'm demanding
anything or goodness knows, making suggestions about how you 'Oh Great
One' should allocate your
[EMAIL PROTECTED] 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
Hello list,
I noticed a problem with cygwin. It seems that some installations of
cygwin running on windows 2000 are leaking memory. The memory leak is
located in some kernel part of the operating system since it is not
cleaned up after all user space applications are close.
This issue is
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
[EMAIL PROTECTED] wrote:
Gosh, isn't there a *win* in *cygwin*?? Not that I'm demanding
anything or goodness knows, making suggestions about how you 'Oh Great
One' should allocate your resources - goodness *no*! But this notion
that a WinDoze problem is not *also* a cyg*win* problem - is quite
I will be happy to find and fix your specific memory leak. My going rate
is $200/hour. If that is satisfactory with you we can talk. If not, you
have the source, the compiler, the debugger, find it yourself or find
someone who will at a lower rate than mine.
Otherwise, bugger off!
--
On Fri, Aug 08, 2003 at 09:32:16AM -0400, [EMAIL PROTECTED] 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
On Thu, Aug 07, 2003 at 11:33:48PM +0100, Sam Edge wrote:
Rolf Campbell [EMAIL PROTECTED] wrote in
[EMAIL PROTECTED]
in gmane.os.cygwin on Thu, 07 Aug 2003 17:44:08 -0400:
Does windows claim to free all memory allocated by a process when it
exits?
It does, even on unexpected terminations.
of folks would be needed first.
Brian Kelly
Christopher Faylor [EMAIL PROTECTED]@cygwin.com on 08/08/2003 11:15:36
AM
Please respond to [EMAIL PROTECTED]
Sent by:[EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc: (bcc: Brian Kelly/WTC1/Empire)
Subject:Re: Win2k and cygwin memory leak
On Thu, Aug 07, 2003 at 12:52:53PM -0400, [EMAIL PROTECTED] wrote:
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.
What a clueless comment.
It is not denial to assert that an OS which allocates memory
Rolf Campbell [EMAIL PROTECTED] wrote in
[EMAIL PROTECTED]
in gmane.os.cygwin on Thu, 07 Aug 2003 17:44:08 -0400:
Does
windows claim to free all memory allocated by a process when it exits?
It does, even on unexpected terminations. (Seg-faults and the like.)
What about cygwin shared
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
I have seen and reported similar problem with cygwin xfree86
i tracked down problem to SeOn kernel memory which means Security
Captured Object Name information.
Thread is Kernel memory leak caused by XWin.exe within cygwin-xfree
mailing list (news.gmane.org:gmane.os.cygwin.xfree)
My system is with
This is the proof.
http://www.faultcentral.org/personal/nedko/soft/pootag.JPG
http://www.faultcentral.org/personal/nedko/soft/taskmanager.JPG
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
you want?
When you cluelessly continue to assert that it's a Cygwin memory leak is
exactly where is leads down the path to character assassinations.
(BTW: Ever think of replacing that Windows box with just a Linux box?)
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem
:18 PM
Sent by:[EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc: (bcc: Brian Kelly/WTC1/Empire)
Subject:Re: Win2k and cygwin memory leak
[EMAIL PROTECTED] wrote:
Well, I can't feel too guilty about chiming me too - cause it
already brought forth a VERY useful and *productive
on it . )
Andrew DeFaria [EMAIL PROTECTED]@cygwin.com on 08/07/2003 06:24:26 PM
Sent by:[EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc: (bcc: Brian Kelly/WTC1/Empire)
Subject:Re: Win2k and cygwin memory leak
[EMAIL PROTECTED] wrote:
It would have been nice
by:[EMAIL PROTECTED]
To:[EMAIL PROTECTED]
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
[EMAIL PROTECTED] wrote:
It has already been
On Fri, Aug 08, 2003 at 09:01:14AM -0400, [EMAIL PROTECTED] wrote:
Seems to little ole *clueless* me, such such issues could be addressed
in that project. Seems like it'd be a heck of lot more congenial and
productive to engage in creative what if scenario's about future
developmemt possibilities
-- Forwarded by Brian Kelly/WTC1/Empire on 08/07/2003
10:07 PM ---
Brian Kelly
08/07/2003 10:06 PM
To:Luc Hermitte [EMAIL PROTECTED]
cc:
Subject:Re: Win2k and cygwin memory leak (Document link: Brian Kelly)
*You're Welcome*
For it *I
Well, you could look at the task manager to see where all the memory is
going (you can enable current memory allocation per process columns).
Also, you could use 'ps' to see if old cygwin processes are still running.
R. Boon wrote:
Hello list,
I noticed a problem with cygwin. It seems that
.
Brian Kelly
[EMAIL PROTECTED]@cygwin.com on 08/07/2003 12:52:53 PM
Sent by:[EMAIL PROTECTED]
To:[EMAIL PROTECTED]
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
This may be a Win2000 problem, not a cygwin problem...What service pack
are you running?
You can try one more thing: after you run out of memory and kill
mozilla, exit all your cygwin processes, and check to see if the
cygwin1.dll file is locked (try renaming it using windows explorer, but,
manufacture! Ain't gonna happen.
BTW, if this program is an effective workaround, I think this will
merit a topic in the FAQ.
You speak as if everybody is experiencing this problem - we aren't!
When you cluelessly continue to assert that it's a Cygwin memory leak
is exactly where is leads down
;-)
bk
Christopher Faylor [EMAIL PROTECTED]@cygwin.com on 08/08/2003 11:13:02
AM
Please respond to [EMAIL PROTECTED]
Sent by:[EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc: (bcc: Brian Kelly/WTC1/Empire)
Subject:Re: Win2k and cygwin memory leak
On Fri, Aug 08, 2003 at 09
[EMAIL PROTECTED] wrote:
Seems like your saying that (using a car analogy) he should replace
the carberator when the real problem is a leak in the fuel line. (IOW
you're attacking the wrong area - your problem lies elsewhere).
Nope - gotta lower your expectations. I use to work in shop when I
I've inserted the results of my test in this message. First the status
before the test, then the status after the test. Also I've used mozilla
as memory buffer. When the system fails and I close an application, like
mozilla, I can execute commands again.
As you can see, ps shows no additional
On Thu, Aug 07, 2003 at 05:08:48PM +0100, chris wrote:
Christopher Faylor wrote:
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
[EMAIL PROTECTED] wrote:
Well, I can't feel too guilty about chiming me too - cause it
already brought forth a VERY useful and *productive* response:
http://cygwin.com/ml/cygwin/2003-08/msg00460.html
Unlike the ... uh-hem ... *posts* of some other folks
This seems to me to be just a
[EMAIL PROTECTED] wrote:
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
:57
AM
Please respond to [EMAIL PROTECTED]
Sent by:[EMAIL PROTECTED]
To:[EMAIL PROTECTED]
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
Christopher Faylor wrote:
As described, the memory leak is obviously not in cygwin. It is in
windows. I was adding some clarification to the issue by changing a
may be to a definitely is.
I think that this kind of clarification is more useful than your
message, which essentially says If we could
* On Thu, Aug 07, 2003 at 08:42:57PM -0700, Andrew DeFaria [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
[You weren't responding to Brian message, but mine.]
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
Christopher Faylor wrote:
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
;-) .
Brian Kelly
Christopher Faylor [EMAIL PROTECTED]@cygwin.com on 08/07/2003 01:56:16
PM
Please respond to [EMAIL PROTECTED]
Sent by:[EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc: (bcc: Brian Kelly/WTC1/Empire)
Subject:Re: Win2k and cygwin memory leak
On Thu, Aug 07, 2003 at 12
the answers I frequently need.
Jim Drash [EMAIL PROTECTED]@cygwin.com on 08/07/2003 04:18:16 PM
Sent by:[EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc: (bcc: Brian Kelly/WTC1/Empire)
Subject:Re: Win2k and cygwin memory leak
I will be happy to find and fix your specific 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
On Thu, Aug 07, 2003 at 05:44:08PM -0400, Rolf Campbell wrote:
Christopher Faylor wrote:
As described, the memory leak is obviously not in cygwin. It is in
windows. I was adding some clarification to the issue by changing a
may be to a definitely is.
I think that this kind of clarification is
45 matches
Mail list logo
