Re: Gnome INSANE shared memory usage
On Fri, Jun 23, 2000 at 11:04:10PM -0700, Kelly Yancey wrote:
Can you guys post the output of:
$ ipcs -bmo | awk -- '/^m/ {num++;total+=$7*$8}; END {print num,(total/4096)}'
taken while you are experiencing the problem. The first number is the total
number of shared memory segments currently active and the second should be the
total number of shared memory pages in use. Thanks,
Kelly
Hi,
just FYI, I don't know whether this is much but my machine is definitely
more lagged compared to when I just started X.
FreeBSD 5.0-CURRENT #6: Mon Jun 5 17:06:37 CEST 2000
(yeah it's a bit out of date...)
$ ipcs -bmo | awk -- '/^m/ {num++;total+=$7*$8}; END {print num,(total/4096)}'
47 1362
Running GNOME 1.2, XFree4 with the ati driver (Dell Optiplex onboard chip).
--Stijn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Sat, 24 Jun 2000, Alexander Sanda wrote:
I'am ready to try another WM and see whether the SHM problems stay or not
(other solutions didn't exactly work, I _dramatically_ increased all the
SHM limits in the kernel but still get tons of shm errors from imlib or
gdk). Yet, I still see excessive shm usage in the output of ipcs (similar
to the output reported by the original poster).
BTW: It's for sure _not_ a -current issue and might have nothing to do
with FreeBSD at all, since I'am running 4.0-STABLE on this machine, with
Xfree 4.0 and Gnome 1.2.
Can you guys post the output of:
$ ipcs -bmo | awk -- '/^m/ {num++;total+=$7*$8}; END {print num,(total/4096)}'
taken while you are experiencing the problem. The first number is the total
number of shared memory segments currently active and the second should be the
total number of shared memory pages in use. Thanks,
Kelly
--
Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA
System Administrator, eGroups.com http://www.egroups.com/
Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/
Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Gnome INSANE shared memory usage
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. I can't find any evidence that I am not the only person on the planet having this problem, but I am completely out of ideas. Does anyone know what's going on here? Look at this output of "icps -mbop", it's ridiculous: Shared Memory: T ID KEYMODE OWNERGROUP NATTCH SEGSZ CPID LPID m 655365432010 --rwa--pgsqlpgsql 2120246246 m 655375432001 --rw---pgsqlpgsql 2 1063936246246 m 655385432007 --rw---pgsqlpgsql 2 96424246246 m 196611 0 --rw-r--r-- rootwheel 7 4096324599 m 262148 0 --rwarwarwachrischris 2 65536410324 m 262149 0 --rwarwarwachrischris 2 65536408324 m 1441798 0 --rw-r--r-- rootwheel 15 4096324 5409 m 1441799 0 --rwarwarwachrischris 2 65536410324 m 262152 0 --rwarwarwachrischris 2 65536410324 m 262153 0 --rwarwarwachrischris 2 65536408324 m 196618 0 --rwarwarwachrischris 2 65536410324 m 131083 0 --rwarwarwachrischris 2 65536402324 m 131084 0 --rwarwarwachrischris 2 65536402324 m 131085 0 --rwarwarwachrischris 2 65536402324 m 131086 0 --rwarwarwachrischris 2 65536402324 m 131087 0 --rwarwarwachrischris 2 65536402324 m 131088 0 --rwarwarwachrischris 2 65536402324 m 131089 0 --rwarwarwachrischris 2 65536400324 m 131090 0 --rwarwarwachrischris 2 65536400324 m 131091 0 --rwarwarwachrischris 2 65536400324 m 131092 0 --rwarwarwachrischris 2 65536400324 m 131093 0 --rwarwarwachrischris 2 65536400324 m 131094 0 --rwarwarwachrischris 2 65536400324 m 131095 0 --rw-r--r-- rootwheel 3 4096324563 m 131096 0 --rwarwarwachrischris 2 65536408324 m 131097 0 --rwarwarwachrischris 2 65536410324 m 131098 0 --rwarwarwachrischris 2 65536408324 m 131099 0 --rwarwarwachrischris 2 65536410324 m 131100 0 --rwarwarwachrischris 2 65536408324 m 131101 0 --rwarwarwachrischris 2 65536408324 m 131102 0 --rwarwarwachrischris 2 65536412324 m 131103 0 --rwarwarwachrischris 2 65536412324 m 131104 0 --rwarwarwachrischris 2 65536412324 m 131105 0 --rwarwarwachrischris 2 65536412324 m 131106 0 --rwarwarwachrischris 2 65536412324 m 65571 0 --rwarwarwachrischris 2 65536412324 m 65572 0 --rw-r--r-- rootwheel 6 4096324599 m 65573 0 --rw-r--r-- rootwheel 8 4096324400 m 65574 0 --rw-r--r-- rootwheel 11 4096324 12638 m 196647 0 --rwarwarwachrischris 2 32768548324 m 196648 0 --rwarwarwachrischris 2 32768548324 m 196649 0 --rwarwarwachrischris 2 32768548324 m 196650 0 --rwarwarwachrischris 2 32768548324 m 196651 0 --rwarwarwachrischris 2 32768548324 m 196652 0 --rwarwarwachrischris 2 32768548324 m 196653 0 --rwarwarwachrischris 2 32768567324 m 262190 0
Re: Gnome INSANE shared memory usage
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). I can't find any evidence that I am not the only person on the planet having this problem, but I am completely out of ideas. Does anyone know what's going on here? Look at this output of "icps -mbop", it's ridiculous: Some time ago I've answered question like this, so let me quote myself: Subject: Re: Shared memory changes in current? Date: Tue, 06 Jun 2000 15:32:19 +0300 From: Maxim Sobolev [EMAIL PROTECTED] To: Alexander Sanda [EMAIL PROTECTED] "It has noting to do with kernel/gnome. XFree 4.0 is known to be very hungry for the shared memory, so you should increase SHMSEG parameter in your kernel config file. There are no guidelines as to what exact number will be sufficient, so you should define it in experimental way. I personally set it to 100 (options SHMSEG=100) and do not see any warnings anymore." -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
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). That is correct. "It has noting to do with kernel/gnome. XFree 4.0 is known to be very hungry for the shared memory, so you should increase SHMSEG parameter in your kernel config file. There are no guidelines as to what exact number will be sufficient, so you should define it in experimental way. I personally set it to 100 (options SHMSEG=100) and do not see any warnings anymore." Unfortunately, these are my current settings: options SHMALL=1025 options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=1025 options SHMMIN=2 options SHMMNI=256 options SHMSEG=128 I can increase it more, but I think this is quite a ridiculous amount of shared memory to be using. Something must be wrong. I am now searching for a way to disable the MIT-SHM extension in the X server, but I think I may have to recompile. -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
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 [EMAIL PROTECTED]:/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 KEYMODE OWNERGROUP NATTCH SEGSZ CPID LPID m 262144 0 --rw-r--r-- rootusers 6 4096285 11546 m 327681 0 --rw-r--r-- rootusers 5 4096285 11546 m 196610 0 --rw-r--r-- rootusers 5 4096285 11546 m 196611 0 --rw-r--r-- rootusers 2 4096285 309 m 131076 0 --rw-r--r-- rootusers 2 4096285 309 m 4063237 0 --rw-r--r-- rootusers 2 4096285 308 m 4456454 0 --rw-r--r-- rootusers 4 4096285 308 m 131092 0 --rw-r--r-- rootusers 2 4096285 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Fri, Jun 23, 2000 at 02:30:42PM -0400, 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). I think you may have a point there. While trying to find out whether XFree86 had an option to disable the MIT-SHM extension (it doesn't as far as I could tell - I ended up editing the binary and NOPping it out) I noticed that some of the code seems to be in the hardware driver area. I'm using a dual-headed configuration with a Voodoo 3 and a Number Nine (S3 ViRGE VX). -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Fri, 23 Jun 2000, Christopher Masto wrote: Unfortunately, these are my current settings: options SHMALL=1025 options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=1025 options SHMMIN=2 options SHMMNI=256 options SHMSEG=128 I can increase it more, but I think this is quite a ridiculous amount of shared memory to be using. Something must be wrong. I have recently seen the same thing with 4.0-STABLE and XF86-4.0. I found that I had to up both SHMSEG and SHMMAXPGS. Specifically, on each machine setting SHMSEG to 100 and SHMMAXPGS to 2048 did the trick. I think that besides using many separate shared memory segments, the segments themselves are somewhat large. Seeing as how XF86-4 is in everyone's future, is there any reason not to nip these sort of problems now and up increase the default values for SHMSEG and SHMMAXPGS? The amount of additional kernel memory required is negligable for modern systems. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
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 - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
At 4:00 PM -0400 6/23/00, Kelly Yancey wrote: 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. Note that Chris (who posted the original message) is also running sawmill/sawfish... (they are the same thing, right?) --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
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. [just trying to halt a possible goose chase] -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
At 16:30 23.06.2000 -0400, Garance A Drosihn wrote: 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. Note that Chris (who posted the original message) is also running sawmill/sawfish... (they are the same thing, right?) Same here. Latest sawfish, and yes, they're the same. The name was changed from sawmill to sawfisch because of some trademark/copyright problems. I'am ready to try another WM and see whether the SHM problems stay or not (other solutions didn't exactly work, I _dramatically_ increased all the SHM limits in the kernel but still get tons of shm errors from imlib or gdk). Yet, I still see excessive shm usage in the output of ipcs (similar to the output reported by the original poster). BTW: It's for sure _not_ a -current issue and might have nothing to do with FreeBSD at all, since I'am running 4.0-STABLE on this machine, with Xfree 4.0 and Gnome 1.2. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
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 - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Sat, Jun 24, 2000 at 12:29:56AM +0200, Alexander Sanda wrote: BTW: It's for sure _not_ a -current issue and might have nothing to do with FreeBSD at all, since I'am running 4.0-STABLE on this machine, with Xfree 4.0 and Gnome 1.2. Which video card/driver are you using? (Mine is tdfx and s3virge) -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Fri, 23 Jun 2000, Garance A Drosihn wrote: At 4:00 PM -0400 6/23/00, Kelly Yancey wrote: 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. Note that Chris (who posted the original message) is also running sawmill/sawfish... (they are the same thing, right?) Sawmill is *very* customizable. As a matter of fact, when I last tried it the default config was kind of bare. However, a lisp wizard can really jazz it up with loads of graphics, etc. So it is possible that Shawn is using a 'simpler' config and Chris is the aforementioned lisp wizard :) Sawmill/sawfish uses imlib, so if Chris is using a config with loads of graphics, it would lend credence to my theory that imlib and XF86-4.0 are interacting to create large/many shared memory segments. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
At 18:41 23.06.2000 -0400, Christopher Masto wrote: BTW: It's for sure _not_ a -current issue and might have nothing to do with FreeBSD at all, since I'am running 4.0-STABLE on this machine, with Xfree 4.0 and Gnome 1.2. Which video card/driver are you using? (Mine is tdfx and s3virge) nVidia GeForce DDR To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
