The memory eater strikes back (2nd attempt to get attention)
Mike York
zombie at voodoo.UUCP
Thu Oct 26 03:01:17 AEST 1989
In article <89Oct21.211825edt.3287 at neat.cs.toronto.edu> moraes at CS.TORONTO.EDU (Mark Moraes) writes:
>Nope. Even if you remove all libraries except for -lmalloc, it still
>grows. You can see the problem over only a couple of iterations by
>printing the value of sbrk(0) after every loop. The break will grow
>steadily when using -lmalloc or amalloc/afree from -lmpc. With libc
>malloc, the BSD4.3 malloc or any other working malloc, the value stays
>constant after the first iteration.
>
>>b) Is it a bug?
>> - known?
>> - fixed when?
>
>Looks like a bug. Not fixed in Irix 3.2, it seems.
Actually, it seems that it IS fixed in 3.2:
I'm running it right now on a 4D/70GT with 8MB and Irix 3.2 -- no
problems. After the first iteration, the value of sbrk(0) remained
constant. On a 4D/70G with 8MB running Irix 3.1, the value of sbrk
does indeed grow, and after 60 iterations, it REALLY slows down.
However, by inserting mallopt(M_MXFAST, 0) in mem.c before the main
loop, the program works as desired under 3.1.
--
Mike York
Boeing Computer Services, Renton, Washington
(206) 234-7724
uw-beaver!ssc-vax!voodoo!zombie
More information about the Comp.sys.sgi
mailing list