Re: The memory usage is ridiculous

OG> When trying to open a 766Mb latin-1 (spanish) file with OG> xemacs-mule, the memory usage when all the way to 2.1Go before OG> xemacs bitched for lack of addressing space (aka, out of OG> memory). Such an expansion ratio is ridiculous. Anyone knows OG> what the hell is going on and whether it's fixable? What version of XEmacs, and if you've got memory checking built in, what does `buffer-memory-usage' tell you? What expansion ratio do you expect? (I'd say from my memory of español that 10% is a grossly generous upper limit, but just to make sure....) As for what's happening, your guess is almost surely better than mine, but FWIW my bet is that after slurping in a 766MB buffer, it then conservatively estimates that the translated buffer could be as big as 3*766MB, and (to avoid thrashing the allocator) tries to grab it in one shot. Also, there's a known leak (reported by Martin) in large string allocation. The cons counter doesn't get bumped. Maybe something similar is happening here? -- 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.