From owner-freebsd-chromium@FreeBSD.ORG  Fri Feb  8 10:00:58 2013
Return-Path: <owner-freebsd-chromium@FreeBSD.ORG>
Delivered-To: freebsd-chromium@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 8CC0BA08
 for <freebsd-chromium@freebsd.org>; Fri,  8 Feb 2013 10:00:58 +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 BFE1B941
 for <freebsd-chromium@freebsd.org>; Fri,  8 Feb 2013 10:00:57 +0000 (UTC)
Received: (qmail 4363 invoked from network); 8 Feb 2013 14:00:49 +0400
Received: from unknown [172.16.10.39]  (HELO virus.mega-net.ru)
 by mail.mega-net.ru with ESMTP; 8 Feb 2013 14:00:49 +0400
Message-ID: <5114CCD1.5050906@mega-net.ru>
Date: Fri, 08 Feb 2013 14:00:49 +0400
From: "Dmitry S. Nikolaev" <dnikolaev@mega-net.ru>
Organization: OOO Meganet-2003
User-Agent: Mozilla/5.0 (X11; FreeBSD i386;
 rv:17.0) Gecko/20130206 Thunderbird/17.0.2
MIME-Version: 1.0
To: freebsd-chromium@freebsd.org
Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57
References: <CAJuc1zNLC-ESojGq9B5-_7qr6EiwGEwxUojBE9fkU0GybEr6nw@mail.gmail.com>
 <1563077977.10385807.1359749865202.JavaMail.root@k-state.edu>
 <CAF6rxgkaqOw_CwikrWOHC26YRHjx8Ade4KORasZn8WzbmYbrVQ@mail.gmail.com>
 <20130203122913.6c0cf4e9@shibato>
 <CANcjpOBFW6xzjtzx36jn_ADSj5zh0dnedXA68=e_HMtr0_EozA@mail.gmail.com>
 <20130204170802.3ed0ac23@shibato>
 <CAF6rxg=gLiSE4C4BMde9DEJVG4bmQQ5Y72RaT0OyzEv5CAyY6Q@mail.gmail.com>
 <51108BE7.8000804@mega-net.ru>
 <CAF6rxg=sQ2qSVFaHtHJvGnzrcT2oh4zWj4XsifWN5vRGczh3-g@mail.gmail.com>
In-Reply-To: <CAF6rxg=sQ2qSVFaHtHJvGnzrcT2oh4zWj4XsifWN5vRGczh3-g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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 <freebsd-chromium.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-chromium>, 
 <mailto:freebsd-chromium-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-chromium>
List-Post: <mailto:freebsd-chromium@freebsd.org>
List-Help: <mailto:freebsd-chromium-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chromium>, 
 <mailto:freebsd-chromium-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Feb 2013 10:00:58 -0000

Hi all.

After last portsnap and portupgrade chrome work fine all day long, no
blank pages and etc. - bug has gone.
I set kern.ipc.shm_allow_removed=1 and compime chrome with all pacthes
including patch-ui__surface__transport_dib_linux.cc.
I`am running on FreeBSD 8.3-STABLE.

With best regards, Dmitry S. Nikolaev

On 05.02.2013 08:38, Eitan Adler wrote:
> On 4 February 2013 23:34, Dmitry S. Nikolaev <dnikolaev@mega-net.ru> wrote:
>> 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.
> Ack.  I misread.  I read as *either* remove patch or set sysctl.  I shall fix.
>