Re: reproducible cygwin memory problems

["emacs user" <emacs_user at hotmail dot com>]

> From: Eli Zaretskii <eliz@gnu.org>

> If I don't miss anything, it remains to be explained why the OP didn't
> see problems with normal buffers.  Could the OP please try visiting
> several large text files, then kill their buffers, invoke the
> `garbage-collect' function ("M-x garbage-collect RET"), and see if the
> memory footprint returns to its original value?

starting emacs -Q: 12,832k
editing a large test file (43,085,936), emacs memory goes up to 55,028k
killing : emacs uses 13,070
and M-x garbage-collect 13,100 or so,

so far it seems that tmemory is returned.  however, using emacs a bit more, 
opening and killing buffers, eventually does lead to memory increase even 
after I kill all buffers and do garbage-collect.

> A few more tests come to mind:
>
>   . Put a breakpoint in sbrk and in mmap, and find out which one is
>     being called when normal text files and image files (both small
>     and large) are visited.

could you please write which .c files and which routines should I be looking 
at slightly more specifically?  thanks...

>   . Visit many small image files (smaller than 256K) and see whether
>     the memory is being returned to the OS.
>
> I'd like to ask the OP to try these and report the results.

_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to 
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/