From owner-freebsd-current Sat Oct 3 21:10:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01457 for freebsd-current-outgoing; Sat, 3 Oct 1998 21:10:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01328 for ; Sat, 3 Oct 1998 21:09:48 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id VAA08474; Sat, 3 Oct 1998 21:09:25 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd008449; Sat Oct 3 21:09:18 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id VAA24864; Sat, 3 Oct 1998 21:09:15 -0700 (MST) From: Terry Lambert Message-Id: <199810040409.VAA24864@usr06.primenet.com> Subject: Re: something is leaking To: eivind@yes.no (Eivind Eklund) Date: Sun, 4 Oct 1998 04:09:15 +0000 (GMT) Cc: alk@pobox.com, current@FreeBSD.ORG In-Reply-To: <19981003154422.30311@follo.net> from "Eivind Eklund" at Oct 3, 98 03:44:22 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 > > swap_pager: suggest more swap space: 124 MB > > > > Another one. First rpc.statd grows to 126MB, now I come home from > > dinner and find that netscape 4.06 is at 89MB. Something is leaking, > > and it is something deep: rpc.statd is elf, and netscape 4.06 is > > a.out, so they have no shared libs in common. > > It is 'normal' that netscape grow to that size. I see it routinely. > Something also touch all of Netscapes memory in some cases (which is > really hatefull, as it makes my box swap-trash). > > I'm not sure this is a bug or not; John Dyson was looking at it to > determine what happened just as he quit FreeBSD (and wasn't sure > whether it was a FreeBSD bug, either, though he said he suspected it > might be.) The shared memory regions are not being "owned" and reference counted correctly. This is either a bug in the X Server, or in netscape. If you use "localhost:0" instead of ":0" as the display, you will disable the use of the MIT SHM extension, and your leak will go away. Hopefully, this will help someone who cares about this (i.e., someone other than myself, since I think X is a tool, not an ends) to fix the problem. Meanwhile, it is a useful workaround for your problem. 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