From owner-freebsd-current@FreeBSD.ORG Thu May 17 15:10:00 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2AD1A1065673 for ; Thu, 17 May 2012 15:10:00 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from springbank.echomania.com (andric.com [IPv6:2001:888:2003:1001:230:48ff:fe51:76b6]) by mx1.freebsd.org (Postfix) with ESMTP id AC2C78FC19 for ; Thu, 17 May 2012 15:09:59 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at springbank.echomania.com Received: from [192.168.1.6] (tensor.andric.com [87.251.56.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by springbank.echomania.com (Postfix) with ESMTPSA id E4234A7071; Thu, 17 May 2012 17:09:40 +0200 (CEST) Message-ID: <4FB514C3.5020908@FreeBSD.org> Date: Thu, 17 May 2012 17:09:55 +0200 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120425 Thunderbird/13.0 MIME-Version: 1.0 To: Chuck Burns References: <20120517011554.5d16067e@serene.no-ip.org> <20120517071141.GL2701@thinkbsd.divinix.org> <4FB4ED23.2040603@gmail.com> In-Reply-To: <4FB4ED23.2040603@gmail.com> X-Enigmail-Version: 1.5a1pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Chrome crashing system (amd64-10.0-CURRENT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2012 15:10:00 -0000 On 2012-05-17 14:20, Chuck Burns 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. Please note the OP is talking about a complete system crash and/or restart, not just chrome itself crashing. > 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 There seem to be several problems with gperftools; compiled with gcc 4.2.1, there are at least 3 failures in its test suite (of 40 tests). Compiled with gcc 4.7 it doesn't even compile, since it erroneously tries to use backtrace_symbols(), which we don't provide. Compiled with clang 3.1, there are 12 failures. I assume this is because it is doing all kinds of tricky things with threads and re-implementing Yet Another Malloc, which seems to be very hard, as recent experience with head has shown. :) In any case, a good start would be to attempt to diagnose all the test failures that occur with clang only, to see if they indicate a problem in gperftools or clang itself.