From owner-freebsd-current Fri Jun 23 15:40: 3 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 65E9F37BA7A; Fri, 23 Jun 2000 15:39:41 -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 SAA91978; Fri, 23 Jun 2000 18:39:31 -0400 (EDT) Date: Fri, 23 Jun 2000 18:39:31 -0400 (EDT) From: Kelly Yancey X-Sender: kbyanc@kronos.networkrichmond.com To: "Jacques A . Vidrine" Cc: Maxim Sobolev , Christopher Masto , gnome-list@gnome.org, current@FreeBSD.ORG Subject: Re: Gnome INSANE shared memory usage In-Reply-To: <20000623165127.A11376@bone.nectar.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, Jacques A . Vidrine wrote: > On Fri, Jun 23, 2000 at 08:22:00PM +0300, Maxim Sobolev wrote: > > Hmm, where my crystal ball... Aha, I see - probably you are using > > Xfree 4.0, while your friend Xfree3.5*. It is where the problem lie > > (see below). > > Well, I use XFree86 4.0 with two displays, and GNOME 1.2, and I don't > have the kind of usage that Christopher has. > I don't think it is gnome per-se. Just switching from WindowMaker to enlightenment was enough to start my XSHM adventure. I suspect the culprit is really imlib/XF86-4.0 interaction. Gnome may contribute to the problem as it uses imlib itself, but enlightenment really gives imlib a workout. 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