Chris,
Thanks for clearing that up. That's a lot better than what you had thought.
Harold
Christopher Faylor wrote:
On Tue, Nov 05, 2002 at 09:07:56PM -0500, Christopher Faylor wrote:
On Tue, Nov 05, 2002 at 05:00:55PM -0500, Harold L Hunt II wrote:
It was mentioned that the memory
On Tue, Nov 05, 2002 at 09:07:56PM -0500, Christopher Faylor wrote:
On Tue, Nov 05, 2002 at 05:00:55PM -0500, Harold L Hunt II wrote:
It was mentioned that the memory size increased when a new X window
(such as an xterm) is opened, but that it does not decrease when that
window is destroyed.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:cygwin-xfree-owner;cygwin.com]On Behalf Of Konstantin N. Kudin
Sent: Monday, November 04, 2002 8:49 PM
To: [EMAIL PROTECTED]
Subject: Re: XFree leaking memory?
Harold
I do not think I am using -rootless since I am running the standard
Of Harold L Hunt II
Sent: Tuesday, November 05, 2002 11:18 AM
To: [EMAIL PROTECTED]
Subject: RE: XFree leaking memory?
Konstantin,
Interesting. So, this appears to be a new memory leak that has nothing to
do with rootless mode.
At this point I think we will need suggestions from others as to how we
be tedious.
Anybody got any suggestions?
Harold
-Original Message-
From: [EMAIL PROTECTED]
[mailto:cygwin-xfree-owner;cygwin.com]On Behalf Of Konstantin N. Kudin
Sent: Monday, November 04, 2002 8:49 PM
To: [EMAIL PROTECTED]
Subject: Re: XFree leaking memory?
Harold
I do
In other words, it might not be able to follow NEW or MALLOC, because the
object format might be too different.
Try the mem_watch tool in the kde-cygwin cvs area
http://sourceforge.net/cvs/?group_id=27249, which hooks any memory relating
call.
$ less README
Memory Watcher
==
This
]On
Behalf Of Ralf Habacker
Sent: Tuesday, November 05, 2002 3:18 PM
To: [EMAIL PROTECTED]
Subject: RE: XFree leaking memory?
In other words, it might not be able to follow NEW or MALLOC, because the
object format might be too different.
Try the mem_watch tool in the kde-cygwin cvs area
http
There is also this tool -
http://devel-home.kde.org/~sewardj/
Not sure if it can be used on Cygwin, but I think it might.
It depends on the glibc and this isn't ported to cygwin yet.
Ralf
It was mentioned that the memory size increased when a new X window
(such as an xterm) is opened, but that it does not decrease when that
window is destroyed. This indicates one of a few things to me:
1) We are not freeing our window privates (directly or indirectly).
This seems plausible,
On Tue, Nov 05, 2002 at 05:00:55PM -0500, Harold L Hunt II wrote:
It was mentioned that the memory size increased when a new X window
(such as an xterm) is opened, but that it does not decrease when that
window is destroyed. This indicates one of a few things to me:
1) We are not freeing our
I ran XWin under Boundschecker with the following parameters: :0 -engine
1 -rootless -lesspointer
Note that I didn't recompile or modify XWin from its current distribution
version to do this.
After starting it, I ran another instance of Boundschecker and under this
one, I started WMAKER.
Once
Hi all
I am using the cygwin + xfree combination for my X server.
I run the program for days on a W2k laptop and put the machine on stand by
every night. W2k and xfree are restarted quite infrequently (once every
2-4 weeks).
I have noticed in Task Manager that XWin process slowly but surely
Konstantin,
Are you using the ``-rootless'' command-line parameter? If so, the
developer of that feature mentioned that there was a memory leak and
that he was working on fixing it. If not, then we might need to look
into your problem as a previously unknown problem.
Harold
Konstantin N.
13 matches
Mail list logo
