Re: [Bug: 21.4.12] memory leak

junq> Seems to be a memory leak. Not on the basis of that graph alone; you're going to have to be a lot more specific about exactly what you're doing. To give an extreme example, xemacs -batch -vanilla -eval '(while t (insert " "))' would behave that way, but there's no leak here. In particular, I have a quiescent XEmacs here that I haven't input into since yesterday, also on Linux (2.4.20, Debian). Memory usage hasn't changed in at least 14 hours. junq> I have no idea how to attach this graph, it's postscript. PNG would be preferable, since XEmacs can display those inline. junq> '--debug=no' '--error-checking=none' Distro sucks. Is there any chance you would be willing to build with --debug=yes? This will add a few hundred KB in the executable and in the VM footprint, but has no effect on performance. Then try the experiment with 'xemacs -vanilla -funcall show-memory-usage', save the memory usage, let xemacs run, and before you kill it, do M-x show-memory-usage and save again (don't overwrite the initial results!) -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.