From owner-freebsd-current Thu Aug 6 01:09:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21909 for freebsd-current-outgoing; Thu, 6 Aug 1998 01:09:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21894 for ; Thu, 6 Aug 1998 01:09:36 -0700 (PDT) (envelope-from freebsd@xaa.iae.nl) Received: from ariel.xaa.iae.nl (ariel.xaa.iae.nl [194.151.75.10]) by esmeralda.xaa.iae.nl (8.8.8/8.8.7) with ESMTP id KAA11000 for ; Thu, 6 Aug 1998 10:09:00 +0200 (MET DST) (envelope-from freebsd@xaa.iae.nl) Received: by ariel.xaa.iae.nl (VMailer, from userid 1008) id A6C5E4556; Thu, 6 Aug 1998 10:08:59 +0200 (CEST) Message-ID: <19980806100859.A312@xaa.iae.nl> Date: Thu, 6 Aug 1998 10:08:59 +0200 From: Mark Huizer To: freebsd-current@FreeBSD.ORG Subject: memory leaks in libc Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message