Date: Mon, 4 Feb 2013 22:08:55 -0500 From: Eitan Adler <lists@eitanadler.com> To: "J.R. Oldroyd" <fbsd@opal.com> Cc: freebsd-chromium@freebsd.org Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57 Message-ID: <CAF6rxg=gLiSE4C4BMde9DEJVG4bmQQ5Y72RaT0OyzEv5CAyY6Q@mail.gmail.com> In-Reply-To: <20130204170802.3ed0ac23@shibato> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4 February 2013 17:08, J.R. Oldroyd <fbsd@opal.com> 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. -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxg=gLiSE4C4BMde9DEJVG4bmQQ5Y72RaT0OyzEv5CAyY6Q>