From owner-freebsd-current Wed Mar 1 3:22:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from merlin.onsea.com (p65s11a01.client.global.net.uk [195.147.139.102]) by hub.freebsd.org (Postfix) with ESMTP id 3F45437C2B0 for ; Wed, 1 Mar 2000 03:22:04 -0800 (PST) (envelope-from dozprompt@onsea.com) Received: from localhost (dozprompt@localhost) by merlin.onsea.com (8.9.3/8.9.3) with ESMTP id UAA02969; Tue, 29 Feb 2000 20:08:45 GMT (envelope-from dozprompt@onsea.com) X-Authentication-Warning: merlin.onsea.com: dozprompt owned process doing -bs Date: Tue, 29 Feb 2000 20:08:45 +0000 (GMT) From: Cliff Rowley To: Christopher Masto Cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: Shared memory - Was: 2 Queries In-Reply-To: <20000229134143.B4903@netmonger.net> 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 > 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. That explains the errors when running xchat, but that doesnt explain Netscape ;) The annoying thing about this is that if a program decides to die because of this error, it seems I've got a 50/50 chance that it's taken out for good. I have to reboot to reclaim memory >:( It'd be nice if we had a utility that could clean out and reclaim the shared memory in 1 swoop. Then we'd be able to shut down XFree86 (and obviously any other apps using shared memory), and get on with life :) (anyone listening?) Cliff Rowley - while (!asleep) { code(); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message