From owner-freebsd-hackers  Thu Jun 22 23:37:42 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id XAA24668
          for hackers-outgoing; Thu, 22 Jun 1995 23:37:42 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA24646
          for <freebsd-hackers@freebsd.org>; Thu, 22 Jun 1995 23:37:39 -0700
Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id XAA00928; Thu, 22 Jun 1995 23:37:36 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id XAA00196; Thu, 22 Jun 1995 23:37:57 -0700
Message-Id: <199506230637.XAA00196@corbin.Root.COM>
To: Charles Henrich <henrich@crh.cl.msu.edu>
cc: freebsd-hackers@freebsd.org
Subject: Re: Memory leak somewhere? 
In-reply-to: Your message of "Fri, 23 Jun 95 02:30:03 EDT."
             <199506230630.CAA09279@crh.cl.msu.edu> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Thu, 22 Jun 1995 23:37:56 -0700
Sender: hackers-owner@freebsd.org
Precedence: bulk

>I've noticed lately that my S3 X server grows continuously (as does my swap
>utilization) as time goes by, and never shrinks.  Currently my X server process
>looks like so:
>
>root       252  0.0 30.9 11632 9440 ??  I    10:39PM    0:21.43 X :0 (XF86_S3)
>
>and has only been running a few hours.  I've talked with the author of the
>Server and he was astonished when I told him I've seen it as high as 15M of
>ram.  He claims he never see's this, however he's running it under Linux.  He
>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?

   The kernel memory allocator has zilch to do with user programs. It's likely
caused by some sort of obscure pixmap alloc/free bug in the X server that you
just happen to trigger because of something you're doing.

-DG