Re: glibc-2.3 new malloc
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
The current issues with pdump are
1. separate dump file (unclean, and paranoid sysadmins wet their
pants when they see big globs of who knows what in a system bindir ;^)
How about putting the dump file is libdir then? ;)
2. poorly localized Lisp data means the first GC puts all of the
Lisp data into "touched" category and it can't be shared any more
Sounds a bit bad for multiuser systems and people like me
who run multiple instances of xemacs on the same machine.
Currently I run four XEmacs sessions on my workstation: one
as a gnus MUA (since Emacs Lisp isn't threaded), one as a
chat client (liece), one for general development, and one in
a tty (in a screen session for remote use). [I realised I
could rationalise that a bit, but I quite like to be able to
restart those individual sessions separately.] So it sounds
like using pdump will result in a bit of performance penalty
wrt memory. But compared to apparent memory leaks perhaps
they is not be so significant.
Jens