Date: Thu, 06 Aug 1998 09:58:19 +0100 From: Karl Pielorz <kpielorz@tdx.co.uk> To: Mark Huizer <freebsd@xaa.iae.nl> Cc: freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc Message-ID: <35C9702B.87B3ED7D@tdx.co.uk> References: <19980806100859.A312@xaa.iae.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
I think I've seen this conversation before... It came up a while ago... I think
it is well know, and apparently very hard to fix... Somone did offer to fix it,
but then declined once it was pointed out exactly how hard it would be to do...
;-)
I think it has something to do with shared memory allocation between shell's -
i.e. exported environment strings or something...
No doubt someone who knows what there talking about will explain it in all it's
gory details why it's not so easy to fix... ;-)
Regards,
Karl
Mark Huizer wrote:
>
> Hi, a nice user of ours pointed me to the fact that various functions
> like setenv, putenv etc leak memory like crazy. To mention a very
> simple example:
>
> main(){while(1){setenv("A","AA",1);setenv("A","A",1);}}
>
> while consume all memory within short periods of time (see setenv.c for
> the reason).
>
> Is this wellknown? I think it is bad, and would like to fix it
>
> Mark
> --
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35C9702B.87B3ED7D>