xfree leaking memory?
Harold L Hunt II
huntharo@msu.edu
Thu Nov 14 09:14:00 GMT 2002
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 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, but I don't think our window privates are even 1
>>>kilobyte.
>>>
>>>
>>I thought I should point out that Cygwin doesn't currently return
>>deallocated memory to the windows pool. So, the heap only gets larger.
>>
>>
>
>I thought I should point out that, while I wrote the function in
>question, the above statement was completely wrong. I was investigating
>sbrk() operation for an unrelated matter and noticed that it was
>dutifully releasing unused memory back to the system.
>
>I don't know why I thought things behaved any differently than this but
>I thought I should correct any misperceptions that I caused.
>
>cgf
>
>
More information about the Cygwin-xfree
mailing list