Date: Thu, 17 May 2012 16:12:15 -0700 From: Evan Martin <evan@chromium.org> To: "Conrad J. Sabatier" <conrads@cox.net> Cc: freebsd-chromium@freebsd.org, John Hixson <john@ixsystems.com>, freebsd-current@freebsd.org Subject: Re: Chrome crashing system (amd64-10.0-CURRENT) Message-ID: <CAFzwtj2aTwgjeRkY0Bg9u10K74Cer4uExKw=fV3Te-i0LJe-%2Bg@mail.gmail.com> In-Reply-To: <20120517180849.72ac2664@serene.no-ip.org> References: <20120517011554.5d16067e@serene.no-ip.org> <CAFzwtj2bh6YaJ%2BkOY4%2BhrSFOSD=rvNoSziBeg0v6skBbQ1hb7Q@mail.gmail.com> <20120517180849.72ac2664@serene.no-ip.org>
index | next in thread | previous in thread | raw e-mail
On Thu, May 17, 2012 at 4:08 PM, Conrad J. Sabatier <conrads@cox.net> wrote: > Thanks. I tried those, and it still locked up. > > I finally just moved away ~/.config/chromium, and it started up OK. > Luckily, I was able to restore pretty much everything from my synced > data. It's a little surprising to me that a userspace app is able to nuke your system, but perhaps the bug is just something mundane like out of control memory allocations and it's just swapping.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFzwtj2aTwgjeRkY0Bg9u10K74Cer4uExKw=fV3Te-i0LJe-%2Bg>