[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Pretest note

From: Carsten Mattner
Subject: Re: Pretest note
Date: Wed, 14 Mar 2012 11:25:35 +0100

On Tue, Mar 13, 2012 at 7:25 AM, Chong Yidong <address@hidden> wrote:
> Carsten Mattner <address@hidden> writes:
>> Don't we want to do something about the leak(s) or at least verify
>> down that they're correct "caching" or "reuse" behavior?
> AFAICT, this is Jan's report that memory is not returned to the system
> on Mac OS?  Obviously, if someone can help pin this down, that will be
> appreciated.  Yamamoto Mitsuharu gave one suggestion here:
> http://lists.gnu.org/archive/html/emacs-devel/2012-01/msg00358.html.
> Also, I'd like to know whether it really involves memory not being
> returned at all, independently of gnutls and networking.  For example,
> here is some Elisp code that visits a file and kills the buffer a few
> thousand times:
> (dotimes (n 50000)
>  (with-temp-buffer
>    (insert-file-contents "/path/to/emacs/etc/NEWS")))

This keeps emacs 99% busy for a couple minutes and increases
the resident size by 1 or 2 MB.

What's more interesting is that today's bzr build
even with -Q and -Q -nw seems to use more than 1.5x times memory
after startup than it used to.

To rule out any issues caused by --without-xml2 I have rebuilt and
it still start Emacs.app at 42MB while it used to start at 25MB.

What did change?

> If Emacs on Mac OS really never returns memory, this should chew up all
> the memory on your system.  Does it?  Check also if Emacs 23 is
> affected.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]