From owner-freebsd-questions@FreeBSD.ORG  Sat Aug  9 06:31:26 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 32E9937B401
	for <freebsd-questions@freebsd.org>;
	Sat,  9 Aug 2003 06:31:26 -0700 (PDT)
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by mx1.FreeBSD.org (Postfix) with SMTP id 02A8D43FE3
	for <freebsd-questions@freebsd.org>;
	Sat,  9 Aug 2003 06:31:25 -0700 (PDT)
	(envelope-from iedowse@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa69058@salmon>; 9 Aug 2003 14:31:24 +0100 (BST)
To: John Mills <john.m.mills@alum.mit.edu>
In-Reply-To: Your message of "Fri, 08 Aug 2003 09:54:04 EDT."
             <Pine.LNX.4.44.0308080945100.4077-100000@localhost.localdomain> 
Date: Sat, 09 Aug 2003 14:31:23 +0100
From: Ian Dowse <iedowse@maths.tcd.ie>
Message-ID: <200308091431.aa69058@salmon.maths.tcd.ie>
cc: FreeBSD-questions <freebsd-questions@freebsd.org>
Subject: Re: Xclock grows and grows (Was Re: How can I check for swap
	space?) 
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Aug 2003 13:31:26 -0000

In message <Pine.LNX.4.44.0308080945100.4077-100000@localhost.localdomain>, Joh
n Mills writes:
>'startx' still proceeds until it fills all available memory. In 
>particular, 'top' shows the size of 'xclock' growing while other processes 
>seem OK.
...
>2) Does this [mis]behavior sound familiar to anyone?

I've seen this before when the "fontconfig" system got confused. Try
running

  fc-cache -fv

as root. If that doesn't fix it, try:

  echo "*clock.render: false" >> /usr/X11R6/lib/X11/app-defaults/XClock

This second command disables the Xrender extensions in xclock, which
I have found necessary on some systems to make xclock work at all.

Ian