Re: Emacs bzr memory footprint

[Eli Zaretskii]

> From: Nix <address@hidden>
> Cc: address@hidden, address@hidden
> Date: Fri, 21 Oct 2011 13:05:42 +0100
> 
> >                                                            If so, the
> > memory allocator used by Emacs should prevent any such fragmentation,
> > at least in the simple scenarios you described.  So I don't think
> > memory fragmentation can explain what you see.
> 
> What, even if what's happening is massive allocation of conses followed
> by allocation of longer-lived stuff followed by freeing of those conses?

I'm really not an expert on this, but I think the answer is YES.  At
least the GNU/Linux build does not use the gmalloc.c and ralloc.c
modules, AFAIK because the native malloc on GNU/Linux includes the
same or superior functionality.