Date: Fri, 23 Jun 2000 14:30:42 -0400 From: Shawn Halpenny <malachai@iname.com> To: Maxim Sobolev <sobomax@FreeBSD.ORG> Cc: Christopher Masto <chris@netmonger.net>, gnome-list@gnome.org, current@FreeBSD.ORG Subject: Re: Gnome INSANE shared memory usage Message-ID: <20000623143041.A27140@cs163.humb.nt.com> In-Reply-To: <39539CB7.FCB177A0@FreeBSD.org> References: <20000623131006.A10060@netmonger.net> <39539CB7.FCB177A0@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 23, 2000 at 01:22:00PM EDT
> Christopher Masto wrote:
>
> > This is a plea for help.
> >
> > I used to have a problem with Gnome - it ate up all of my SysV shared
> > memory. My window manager (sawmill) 's title bars would come up blank
> > because of this. I eventualy found the "use MIT-SHM" checkbox in the
> > imlib settings and turned it off, and the problem mostly went away.
> >
> > I have recently upgraded to Gnome 1.2 and it has come back with a
> > vengence. The checkbox no longer has any effect. I have bumped up
> > the amount of shared memory, but it all gets used, no matter how much
> > is available. It is driving me crazy. I can't run other programs
> > (samba, fxtv) because there is never any shared memory left. Something
> > is eating it all - gnome, gtk, imlib, I don't know how these pieces
> > fit together or exactly where the fault lies. I am desperately looking
> > for a solution that doesn't involve just giving up this very pleasant
> > and otherwise useful software.
> >
> > I have asked a co-worker who also runs Gnome on FreeBSD to check his
> > shared memory usage, and it was fine. The only difference is that I
> > am running -current and he has 4.0-release.
>
> 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).
Here, I'm not running Gnome or -current, but I am running sawfish
(sawmill) and Xfree 4.0:
~% uname -v
FreeBSD 4.0-STABLE #13: Wed Jun 21 13:48:15 EDT 2000
root@nightrain.humb.nt.com:/usr/src/sys/compile/NIGHTRAIN
~% X -version
XFree86 Version 4.0 / X Window System
(protocol Version 11, revision 0, vendor release 6400)
Release Date: 8 March 2000
If the server is older than 6-12 months, or if your card is newer
than the above date, look for a newer version before reporting
problems. (see http://www.XFree86.Org/FAQ)
Operating System: FreeBSD 4.0-CURRENT i386 [ELF]
Module Loader present
~% sawfish --version
sawfish version 0.27.1
~% uptime
2:12PM up 16:43, 5 users, load averages: 0.85, 0.77, 0.72
~% ipcs -mbop
Shared Memory:
T ID KEY MODE OWNER GROUP NATTCH SEGSZ CPID LPID
m 262144 0 --rw-r--r-- root users 6 4096 285 11546
m 327681 0 --rw-r--r-- root users 5 4096 285 11546
m 196610 0 --rw-r--r-- root users 5 4096 285 11546
m 196611 0 --rw-r--r-- root users 2 4096 285 309
m 131076 0 --rw-r--r-- root users 2 4096 285 309
m 4063237 0 --rw-r--r-- root users 2 4096 285 308
m 4456454 0 --rw-r--r-- root users 4 4096 285 308
m 131092 0 --rw-r--r-- root users 2 4096 285 11766
PID 11546 is an xterm, as is 308. 309 is sawfish. 11766 has gone away.
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).
--
Shawn Halpenny | Maniacal@I Ache, Ohm | "Universal Danger!"
+- - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - \
| vi:G3kfM~lxfAPXh~l~2x2FirllpfcxlrifaprmfOX~Xp2hr.lrcelyl2p
- - - - - - - -| fU~X~refsPprnlxppri2lxlpr,pFrpprrfaPlpfiprgllxp~3Xlpfndw
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000623143041.A27140>