Jerry James writes:
I ran the latest Mercurial XEmacs under valgrind for awhile tonight,
just because I really enjoy using such a slow editor. :-) When I
exited, the leak check reported some lost blocks; i.e., memory that
was malloced but not freed. The leaked memory looks to be mostly Lisp
objects. Does this imply a garbage collector leak? Here are the
relevant entries.
Well, most of it looks to be in Xft. Why am I not surprised.
Some of the stuff in Xft is supposed to be refcounted, but what you do
and don't have to manage explicitly is nowhere documented.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta