On Tue, Feb 29, 2000 at 03:57:19PM -0600, Ade Lovett wrote:
> On Tue, Feb 29, 2000 at 01:41:43PM -0500, Christopher Masto wrote:
> > 
> > In any case, one major offender is imlib.  Since I've recently gone
> > Gnome, I've had to turn off imlib's "MIT-SHM shared memory" option
> > or things would go bad after a few minutes or hours of use.
> 
> Can you expand a bit on "go bad"?  I have a couple of machines here
> running with GNOME for days on end with no shared memory problems.

Title bars in sawmill suddenly turning black, GNOME pixmaps
disappearing/getting corrupted, that sort of thing.

> I'm not seeing any leaks, though:
[...]
> Shared Memory:
> T     ID     KEY        MODE       OWNER    GROUP  SEGSZ  CPID  LPID
> m  65536    2622055 --rw-r--r--     root    wheel 1048576    298    298
> m 41615362     792064 --rw-rw-rw-      ade    staff      4  12549  12549

Funny, I even have the option turned off and I've still got:

chris@lion-around:~$ ipcs -bpm
Shared Memory:
T     ID     KEY        MODE       OWNER    GROUP  SEGSZ  CPID  LPID
m  65536    5432010 --rwa------    pgsql    pgsql    120    204    204
m  65537    5432001 --rw-------    pgsql    pgsql 1063936    204    204
m  65538    5432007 --rw-------    pgsql    pgsql  96424    204    204
m 196611          0 --rw-r--r--     root    wheel   4096    837  53838
m 131076          0 --rw-r--r--     root    wheel   4096    837  55434
m 3211269          0 --rwarwarwa    chris    chris 1420800  41206  41206
m 1310726          0 --rw-r--r--     root    wheel   4096    837  55429
m 1310727          0 --rwarwarwa    chris    chris  65536    934    837
m 131080          0 --rw-r--r--     root    wheel   4096    837    926
m 131081          0 --rwarwarwa    chris    chris  65536    934    837
m 131082          0 --rwarwarwa    chris    chris  65536    934    837
m 196619          0 --rw-r--r--     root    wheel   4096    837    934

Still, it's not just me.  Several friends have come to me after my
recommendation that they try sawmill+GNOME with the complaint that their
title bars were getting messed up, and turning of MIT-SHM solved it.
One is running -current, another is running 3.4-RELEASE.  And I've
heard the same thing on the mailing lists.
-- 
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

Reply via email to