From owner-freebsd-chromium@FreeBSD.ORG Sun Feb 3 17:29:18 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2063BDC for ; Sun, 3 Feb 2013 17:29:18 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by mx1.freebsd.org (Postfix) with ESMTP id D28AD224 for ; Sun, 3 Feb 2013 17:29:17 +0000 (UTC) Received: from pool-151-203-245-187.bos.east.verizon.net ([151.203.245.187] helo=homobox.opal.com) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1U23NV-000BGq-1D for freebsd-chromium@freebsd.org; Sun, 03 Feb 2013 17:29:17 +0000 Received: from shibato (shibato.opal.com [IPv6:2001:470:8cb8:4:221:63ff:fe5a:c9a7]) (authenticated bits=0) by homobox.opal.com (8.14.4/8.14.4) with ESMTP id r13HTETE054139 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sun, 3 Feb 2013 12:29:15 -0500 (EST) (envelope-from fbsd@opal.com) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 151.203.245.187 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18OHbaZmiLDLNYPdG13Apmd Date: Sun, 3 Feb 2013 12:29:13 -0500 From: "J.R. Oldroyd" To: freebsd-chromium@freebsd.org Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57 Message-ID: <20130203122913.6c0cf4e9@shibato> In-Reply-To: References: <1563077977.10385807.1359749865202.JavaMail.root@k-state.edu> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (homobox.opal.com [IPv6:2001:470:8cb8:4::1]); Sun, 03 Feb 2013 12:29:15 -0500 (EST) X-Spam-Status: No, score=-2.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, RP_MATCHES_RCVD shortcircuit=no autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on homobox.opal.com X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 17:29:18 -0000 On Sat, 2 Feb 2013 09:16:36 -0500 Eitan Adler wrote: > > I am seeing the same issue. And +1 here. I think the problem may be related to files/patch-ui__surface__transport_dib_linux.cc which replaces the immediate removal of the shm after attaching to it with removal in the destructor iff we're the last who is attached to it. The comment states: // On BSD we can't access the shared memory after is marked for deletion. but this is not true if kern.ipc.shm_allow_removed=1 which we are told to set in the pkg-message. I have removed this patch and am running with the original code. All appears well so far, but perhaps I have not been running long enough for the problem to recur. I'll post back if it it does. Of course, the original code is defensive to ensure that the shm is removed if there's a crash. Presumably, the fact that the code in the patch isn't working suggests that something is, in fact, crashing. Perhaps this is what really should be debugged. -jr