From owner-freebsd-chromium@FreeBSD.ORG Tue Feb 5 04:34:51 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 DA22C47D for ; Tue, 5 Feb 2013 04:34:51 +0000 (UTC) (envelope-from dnikolaev@mega-net.ru) Received: from mail.mega-net.ru (mail.mega-net.ru [91.217.137.1]) by mx1.freebsd.org (Postfix) with SMTP id ED37568F for ; Tue, 5 Feb 2013 04:34:50 +0000 (UTC) Received: (qmail 83161 invoked from network); 5 Feb 2013 08:34:48 +0400 Received: from unknown [172.16.10.39] (HELO virus.mega-net.ru) by mail.mega-net.ru with ESMTP; 5 Feb 2013 08:34:48 +0400 Message-ID: <51108BE7.8000804@mega-net.ru> Date: Tue, 05 Feb 2013 08:34:47 +0400 From: "Dmitry S. Nikolaev" Organization: OOO Meganet-2003 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130114 Thunderbird/17.0.2 MIME-Version: 1.0 To: Eitan Adler Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57 References: <1563077977.10385807.1359749865202.JavaMail.root@k-state.edu> <20130203122913.6c0cf4e9@shibato> <20130204170802.3ed0ac23@shibato> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: dnikolaev@mega-net.ru List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 04:34:51 -0000 Hi all. I have the same problem with chrome. Eitan Adler, you need to read J.R. Oldroyd message. You must set sysctl, than remove patch files/patch-ui__surface__transport_dib_linux.cc, than recompile chrome. I will try this fix today, hope it will work. --- With best regards, Dmitry S. Nikolaev On 05.02.2013 07:08, Eitan Adler wrote: > On 4 February 2013 17:08, J.R. Oldroyd wrote: >> I can say that I've run without the patch for about 36-48 hours now >> and the problem has not recurred. So those wanting a simple fix can >> simply remove the patch, recompile chrome, set >> kern.ipc.shm_allow_removed=1 >> and run. > I have this set and it does *not* fix the problem for me. >