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 o
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 a
sting.
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
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 some
-- 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'r
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 possibil
on 08/07/2003 10:48:57
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 Fri, Aug 08, 2003 at 03:44:11AM +0200, Luc Hermitte wrote:
>* On Thu, Aug 07, 2003 at 03:2
* On Thu, Aug 07, 2003 at 03:24:26PM -0700, Andrew DeFaria <[EMAIL PROTECTED]> 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 t
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: http://cy
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 w
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 acknowledged several times over that it is not a
>>problem of Cygwin's rather a problem of Windows.
>
>I think we all agree to t
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
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
BK
"Andrew DeFaria" <[EMAIL PROTECTED]>@cygwin.com on 08/07/2003 11:28: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 fee
patient.
Cluelessly yours,
BK
( PS - I HATE Windows - put I get paid 'quite well' to work on it, and
given the current state
of the economy - I think I'll keep working on it . )
"Andrew DeFaria" <[EMAIL PROTECTED]>@cygwin.com on 08/07/2003 06:24:26 PM
Sent
hink more
feedback
and experience from a wider cross section 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 PROTECT
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 terminati
[EMAIL PROTECTED] wrote:
It would have been "nice" if there was an acknowledgement of this
problem (cygwin's or not) rather than attempted character assassinations.
It has already been acknowledged several times over that it is not a
problem of Cygwin's rather a problem of Windows. What else do
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
[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 quit
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!"
--
Unsubs
: 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,
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 reporte
[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 th
AIL PROTECTED]>@cygwin.com on 08/07/2003 02:58:10 PM
Sent by:[EMAIL PROTECTED]
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 "dema
[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 wa
;-)
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,
[EMAIL PROTECTED] 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.
Funny I don't see the problem. (Anybody else?)
Hen
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,
r
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, a
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 proc
* 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
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 c
t;--
> "Christopher Faylor" <[EMAIL PROTECTED]>@cygwin.com on
> 08/07/2003 11:40:57
> AM
>
> Please respond to [EMAIL PROTECTED]
>
> Sent by:[EMAIL PROTECTED]
>
>
> To:[EMAIL PROTECTED]
> cc: (bcc: Brian Kelly/WTC1/Empire)
>
> Sub
[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 o
[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 band
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 clar
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.
h the *meanness* here is small price to
pay to get 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 c
that keep
cyg*win*
from working - all along *denying* it's a cyg*win* problem .
Interesting how a 'Great' mind works ;-) .
Brian Kelly
"Christopher Faylor" <[EMAIL PROTECTED]>@cygwin.com on 08/07/2003 01:56:16
PM
Please respond to [EMAIL PROTECTED]
Se
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
41 matches
Mail list logo
