From owner-freebsd-current Sun Oct 4 17:07:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22369 for freebsd-current-outgoing; Sun, 4 Oct 1998 17:07:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22361 for ; Sun, 4 Oct 1998 17:07:56 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id RAA05254; Sun, 4 Oct 1998 17:07:35 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp02.primenet.com, id smtpd005196; Sun Oct 4 17:07:26 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id RAA09492; Sun, 4 Oct 1998 17:07:21 -0700 (MST) From: Terry Lambert Message-Id: <199810050007.RAA09492@usr09.primenet.com> Subject: Re: something is leaking To: mike@smith.net.au (Mike Smith) Date: Mon, 5 Oct 1998 00:07:20 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, eivind@yes.no, alk@pobox.com, current@FreeBSD.ORG In-Reply-To: <199810042051.NAA06504@dingo.cdrom.com> from "Mike Smith" at Oct 4, 98 01:51:39 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Try it before you comment. You can't really argue with success. As I > > said, I've been unwilling to track it down. > > I don't know how you come to the conclusion that I haven't tried it, > especially when I explicitly stated that I had. > > There is a hard limit on the amount of SYSV shared memory that can be > allocated. Even on systems without it enabled, Netscape still blows > out to a ridiculous size, way beyond this value. I can guarantee Netscape won't grow out of all proportion if you run it on a machine other than the machine where the display is running, since I and a number of collegues have been doing it this way for a year or more without the crashes that everyone complains about. If you can get the client to make a network rather than a POSIX domain socket connection, you can get the same effect with a locally run client. The problem is managing disconnects, and tracking memory in use by client rather than by socket. Techincally, you could argue breakage in either libX or in the X server, depending on what side of the fence your feet were hanging over on any given day. In any case, if you provide a resource tracking mechanism to distinguish one program from another, the problem goes away. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message