cdl@chiton.ucsd.edu (Carl Lowenstein) (05/29/91)
I have noticed that NeXTmille seems to be a memory hog. Last month,
when I had only 8MB in my cube, the program would become unuseable
about 1/2-way through the first game, due to excessive swapping.
Now, with 24MB, it is good for about 2 1/2 games. The 'pages free'
shown by vm_stat gets down to about 30 or so, and never recovers.
Memory allocation seems to get very tangled up (to use a non-technical
term), and does not recover when I quit the game. Nor even if I log
out and back in again. The only thing that recovers memory into the
'pages free' is a reboot.
There is nothing obvious when I link NeXTmille with the MallocDebug
library and look for memory leaks.
Comments or suggestions are welcome.
--
carl lowenstein marine physical lab u.c. san diego
{decvax|ucbvax} !ucsd!mpl!cdl cdl@mpl.ucsd.edu
clowenstein@ucsd.edu