> I know, I'm saying the memory usage *reported by XEmacs* seems > reasonable. The bloat is not accounted for by objects we count, not > even as a proportion, right? Indeed not: `object-memory-usage-stats' reports sane values. The problem is the actual amount of memory allocated (which is all, or nearly all, traversed by the garbage collector: RSS goes up just as fast as VSZ.) ... hm. I just remembered Ulrich Drepper and Wolfram Gloger mentioning (I think on libc-alpha a while back but it may have been in some paper somewhere) that the glibc malloc hooks are pretty much completely broken and don't work properly, especially in glibc 2.4+: as far as I can tell we don't rely on those hooks except when terminating (to a very limited degree) and as a debugging hack with no effect on memory-allocation semantics, right? (if so, damn, I'll have to actually do some *work* to diagnose this rather than leaping directly to the solution by magic. :) )