Date: Sat, 09 Aug 2003 14:31:23 +0100 From: Ian Dowse <iedowse@maths.tcd.ie> To: John Mills <john.m.mills@alum.mit.edu> Cc: FreeBSD-questions <freebsd-questions@freebsd.org> Subject: Re: Xclock grows and grows (Was Re: How can I check for swap space?) Message-ID: <200308091431.aa69058@salmon.maths.tcd.ie> In-Reply-To: Your message of "Fri, 08 Aug 2003 09:54:04 EDT." <Pine.LNX.4.44.0308080945100.4077-100000@localhost.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200308091431.aa69058>