Ar an t-ochtú lá déag de mí na Nollaig, scríobh Stephen J. Turnbull:
> On 17 Dec 2006, nix(a)esperi.org.uk verbalised:
> > I just upgraded to latest CVS (2006-12-16, 21:20) to try to dig
> > further into this KKCC-related (?) memory leak. (I'll know for
> > sure if it's KKCC-related in an hour or so.)
> It isn't KKCC. I've built an Emacs without newgc and --without-kkcc.
> At boot:
> RSS VSZ
> 76043 82104
> Yet half an hour later, after reading 500-odd posts on the
> spamassassin mailing list in Gnus:
> RSS VSZ
> 275404 287840
> Half of this appears unused. I'm going to get some stats out
> of malloc() next, to see if arena fragmentation is at fault.
The reported memory doesn't seem unreasonable; Gnus conses like it's
going out of style. (Yeah, I know you'd like to go back to 2-word
conses and save 15% of that, but that's not in the cards.)
Is this an Xft build? It's hard to get Xt/Xlib stats, as you know,
but Xft does provide some hooks for its memory usage.
Nix seems to use XFT builds primarily right now. I see the same behaviour on
a non-KKCC build with server-side fonts--my solution so far has been:
derrick [ cat ~/bin/unlimited-xemacs
ulimit -d unlimited
ulimit -c unlimited
exec /usr/local/bin/xemacs $*
but that’s a long way from being the Right Thing. On the TTY build I
normally use for reading mail, it leaks, but not as badly:
with 20078197 as the show-memory-usage output. (I have an RSS ulimit of
46080K there, however, so opening a decent-size mailbox gives me an
out-of-memory error.) This means the leaking is not X11 specific.
I don’t use KKCC in general, because it has been less responsive for me than
the old GC. If I remember correctly, however, its summaries of memory usage
were more accurate, to some extent.
When I was in the scouts, the leader told me to pitch a tent. I couldn't
find any pitch, so I used creosote.
XEmacs-Beta mailing list