From owner-freebsd-current@FreeBSD.ORG Fri May 18 08:45:51 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 40535106564A; Fri, 18 May 2012 08:45:51 +0000 (UTC) (envelope-from conrads@serene.no-ip.org) Received: from eastrmfepo203.cox.net (eastrmfepo203.cox.net [68.230.241.218]) by mx1.freebsd.org (Postfix) with ESMTP id B543C8FC0C; Fri, 18 May 2012 08:45:50 +0000 (UTC) Received: from eastrmimpo209.cox.net ([68.230.241.224]) by eastrmfepo203.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20120518084550.LXUR18532.eastrmfepo203.cox.net@eastrmimpo209.cox.net>; Fri, 18 May 2012 04:45:50 -0400 Received: from serene.no-ip.org ([98.164.83.188]) by eastrmimpo209.cox.net with bizsmtp id BLlp1j00A43nm9e02LlpVL; Fri, 18 May 2012 04:45:49 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020207.4FB60C3D.00B0,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=LKDkrRjixwgtmuXwrIwnijc/8ro9lGx9B3c+ChRocFo= c=1 sm=1 a=z1TLwsU0kBEA:10 a=swW3mUodPN4A:10 a=G8Uczd0VNMoA:10 a=8nJEP1OIZ-IA:10 a=F4D4Y6gUi4XSUMrqnG4xkg==:17 a=kviXuzpPAAAA:8 a=-_rlT6ndqfEwl-SpOPUA:9 a=wPNLvfGTeEIA: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 q4I8jnmL004910; Fri, 18 May 2012 03:45:49 -0500 (CDT) (envelope-from conrads@serene.no-ip.org) Received: (from conrads@localhost) by serene.no-ip.org (8.14.5/8.14.5/Submit) id q4I8jh1J004909; Fri, 18 May 2012 03:45:43 -0500 (CDT) (envelope-from conrads) Date: Fri, 18 May 2012 03:45:43 -0500 From: "Conrad J. Sabatier" To: Evan Martin Message-ID: <20120518084543.GB1264@serene.no-ip.org> References: <20120517011554.5d16067e@serene.no-ip.org> <20120517180849.72ac2664@serene.no-ip.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: "Conrad J. Sabatier" , 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: Fri, 18 May 2012 08:45:51 -0000 On Thu, May 17, 2012 at 04:12:15PM -0700, Evan Martin wrote: > On Thu, May 17, 2012 at 4:08 PM, Conrad J. Sabatier 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. I just discovered while poking around again under ~/.config that my old chromium directory (that is, the directory file itself) had somehow become corrupted. This was most likely what was causing chrome to go berserk before. I'm using SU+J here, and this problem wasn't detected by fsck before. I only discovered it this evening when, after having already deleted all of the files in the directory, rmdir failed with the error message "Directory not empty". After booting single-user and running fsck twice (to force it not to use the journal), looks like everything's back to normal now. -- Conrad J. Sabatier conrads@cox.net