From owner-freebsd-hackers Fri Jun 23 02:36:50 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA00609 for hackers-outgoing; Fri, 23 Jun 1995 02:36:50 -0700 Received: from elbe.desy.de (elbe.desy.de [131.169.82.208]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA00601 for ; Fri, 23 Jun 1995 02:36:48 -0700 From: Lars Gerhard Kuehl Date: Fri, 23 Jun 95 11:37:49 +0200 Message-Id: <9506230937.AA26679@elbe.desy.de> To: roberto@blaise.ibp.fr Subject: Re: Memory leak somewhere? Cc: freebsd-hackers@FreeBSD.ORG Sender: hackers-owner@FreeBSD.ORG Precedence: bulk >> suggests perhaps there is a problem with something somewhere in FreeBSD. This >> behaviour seems to be new with the 0412-SNAP, although I dont have any >> proof of this. This is crazy, I have a 32mb machine, and its performing like >> a dog because of this sort of memory usage (!) :(. On a 16mb machine, if you >> run any significant apps you go to swaphell because of the memory usage here. >> Could this be a leak in the kernel malloc, or mmap code or some such? > Relink the server with either -lgnumalloc or -ldlmalloc (found in ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > ports/devel/libdlmalloc). The libc's malloc take as much as two times the > memory needed per allocation. That may reduce memory loss, but doesn't really solve the problem. Unused memory needs to be actually released. I've often seen XFree servers with VSZ > 25000 kB. My XFree_S3 server at home uses to grow about 3-4 MB/h under normal circumstances, sometimes (in particular in interaction with xman) much more. Even 2 MB/h is too much. I'm afraid there is a longer debugging session required :-( Lars