From owner-freebsd-current Fri Jun 23 13: 1: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from kronos.networkrichmond.com (kronos.networkrichmond.com [64.240.180.22]) by hub.freebsd.org (Postfix) with ESMTP id 81AE837B89C; Fri, 23 Jun 2000 13:01:00 -0700 (PDT) (envelope-from kbyanc@posi.net) X-Provider: Network Richmond, LLC. http://www.networkrichmond.com/ Received: from localhost (kbyanc@localhost) by kronos.networkrichmond.com (8.9.3/8.9.3/antispam) with ESMTP id QAA89737; Fri, 23 Jun 2000 16:00:53 -0400 (EDT) Date: Fri, 23 Jun 2000 16:00:53 -0400 (EDT) From: Kelly Yancey X-Sender: kbyanc@kronos.networkrichmond.com To: Shawn Halpenny Cc: Maxim Sobolev , Christopher Masto , gnome-list@gnome.org, current@FreeBSD.ORG Subject: Re: Gnome INSANE shared memory usage In-Reply-To: <20000623143041.A27140@cs163.humb.nt.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Jun 2000, Shawn Halpenny wrote: > > I have not had any of the problems he's describing. I have never modified > my shared memory settings in my kernel config either. If the problem is > indeed Xfree 4.0, then I guess it must be a driver issue (I'm using > the neomagic driver). > You are running sawfish, and I'm willing to bet a not very graphics intensive config at that. Try running enlightenment with the default config. The problem may not be solely attributable to XF86-4, but rather a combination of XF86-4 and imlib's aggressive use of shared memory. I suspect if you select a window manager with more eye-candy, you'll see the same results. Kelly -- Kelly Yancey - kbyanc@posi.net - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message