Date: Thu, 17 May 2012 19:58:33 -0500 From: "Conrad J. Sabatier" <conrads@cox.net> To: Chuck Burns <break19@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Chrome crashing system (amd64-10.0-CURRENT) Message-ID: <20120517195833.382c95ee@serene.no-ip.org> In-Reply-To: <4FB4ED23.2040603@gmail.com> References: <20120517011554.5d16067e@serene.no-ip.org> <20120517071141.GL2701@thinkbsd.divinix.org> <4FB4ED23.2040603@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 17 May 2012 07:20:51 -0500 Chuck Burns <break19@gmail.com> wrote: > On 5/17/2012 2:11 AM, John Hixson wrote: > > On Thu, May 17, 2012 at 01:15:54AM -0500, Conrad J. Sabatier wrote: > >> For the last week or so, I've been unable to run chrome. Any > >> attempt to start it up will cause the system either to freeze up > >> or reboot. > > > > To add to this, I've had the same problem on 10-CURRENT for several > > months now. > > Are you guys building ports with clang? There's a known bug with > google-perftools, when it's built with clang, chrome will crash upon > launch. > > > chrome itself can be built with any compiler, but if google-perftools > is built with clang, crash! > > http://code.google.com/p/gperftools/issues/detail?id=394 > Ah, yes, I remember you mentioning this a month or two ago (at least, I think it was you). Thanks for the reminder. I'm gonna make sure my /etc/make.conf specifies gcc for that port. -- Conrad J. Sabatier conrads@cox.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120517195833.382c95ee>