From owner-freebsd-current@FreeBSD.ORG Thu May 17 23:08:57 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 D84A3106566B; Thu, 17 May 2012 23:08:57 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo201.cox.net (eastrmfepo201.cox.net [68.230.241.216]) by mx1.freebsd.org (Postfix) with ESMTP id 5C1678FC08; Thu, 17 May 2012 23:08:56 +0000 (UTC) Received: from eastrmimpo210.cox.net ([68.230.241.225]) by eastrmfepo201.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20120517230856.RSFX5450.eastrmfepo201.cox.net@eastrmimpo210.cox.net>; Thu, 17 May 2012 19:08:56 -0400 Received: from serene.no-ip.org ([98.164.83.188]) by eastrmimpo210.cox.net with bizsmtp id BB8v1j00543nm9e02B8v3C; Thu, 17 May 2012 19:08:55 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020207.4FB58508.000F,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=zgrfwPxMZK8qZ92ObMQftE+CrxUcpQPkHWvi4UAp5mI= c=1 sm=1 a=swW3mUodPN4A:10 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=F4D4Y6gUi4XSUMrqnG4xkg==:17 a=cm27Pg_UAAAA:8 a=jngkN49NAAAA:8 a=kviXuzpPAAAA:8 a=ye2Y2kOJyop1Br4zxMIA:9 a=CjuIK1q_8ugA:10 a=zv9_9hqRWm8A:10 a=4vB-4DCPJfMA:10 a=F4D4Y6gUi4XSUMrqnG4xkg==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from serene.no-ip.org (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id q4HN8s8Z001471; Thu, 17 May 2012 18:08:54 -0500 (CDT) (envelope-from conrads@cox.net) Date: Thu, 17 May 2012 18:08:49 -0500 From: "Conrad J. Sabatier" To: Evan Martin Message-ID: <20120517180849.72ac2664@serene.no-ip.org> In-Reply-To: References: <20120517011554.5d16067e@serene.no-ip.org> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-chromium@freebsd.org, John Hixson , 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 23:08:57 -0000 On Thu, 17 May 2012 08:55:49 -0700 Evan Martin wrote: > These kinds of hard locks often point at graphics driver problems, but > normally Chrome relies on a driver whitelist that likely doesn't > include any FreeBSD drivers. Did you perhaps set a flag somewhere to > bypass a blacklist? > > You could try some command line flags like > --blacklist-accelerated-compositing > --blacklist-webgl > to see if they help. > > (I found those on > http://peter.sh/experiments/chromium-command-line-switches/ , not > certain if they do what you need.) > > Another idea is to use strace/ktrace/truss into a log file to see what > it was doing around the time of dying. 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. Happy ending. :-) -- Conrad J. Sabatier conrads@cox.net