From owner-freebsd-current@FreeBSD.ORG Thu May 17 23:26:45 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 253F5106566C; Thu, 17 May 2012 23:26:45 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo102.cox.net (eastrmfepo102.cox.net [68.230.241.214]) by mx1.freebsd.org (Postfix) with ESMTP id 87A718FC08; Thu, 17 May 2012 23:26:44 +0000 (UTC) Received: from eastrmimpo210.cox.net ([68.230.241.225]) by eastrmfepo102.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20120517232637.PXJF26743.eastrmfepo102.cox.net@eastrmimpo210.cox.net>; Thu, 17 May 2012 19:26:37 -0400 Received: from serene.no-ip.org ([98.164.83.188]) by eastrmimpo210.cox.net with bizsmtp id BBSZ1j00B43nm9e02BSb3C; Thu, 17 May 2012 19:26:37 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020209.4FB5892D.0059,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=8nJEP1OIZ-IA:10 a=F4D4Y6gUi4XSUMrqnG4xkg==:17 a=cm27Pg_UAAAA:8 a=kviXuzpPAAAA:8 a=oCjSQ2ZfFCm5Fb19x00A:9 a=lDoC0UDEdsZUMbiPfIEA:7 a=wPNLvfGTeEIA: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 q4HNQVA8001590; Thu, 17 May 2012 18:26:32 -0500 (CDT) (envelope-from conrads@cox.net) Date: Thu, 17 May 2012 18:26:26 -0500 From: "Conrad J. Sabatier" To: Evan Martin Message-ID: <20120517182626.17c27855@serene.no-ip.org> In-Reply-To: References: <20120517011554.5d16067e@serene.no-ip.org> <20120517180849.72ac2664@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=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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:26:45 -0000 On Thu, 17 May 2012 16:12:15 -0700 Evan Martin wrote: > On Thu, May 17, 2012 at 4:08 PM, Conrad J. Sabatier > wrote: > > Thanks. =A0I 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. >=20 > 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. Yes, that *is* a little troubling. I'm always touting FreeBSD to people as being a rock-solid platform, so I was slightly embarrassed when this happened several times recently when I had a friend over. :-) I'm looking into some sysctl settings now that do seem to have the ability to trigger odd behavior with certain apps, e.g., kern.maxfiles, kern.maxfilesperproc, various shared mem settings, etc. Some apps will either mysteriously refuse to run, or crash just after startup, depending on the settings of these and similar. My chrome problem was no doubt related to my recently having tinkered with some chrome://flags settings. Conservatism and caution definitely seem to be called for with these! :-) --=20 Conrad J. Sabatier conrads@cox.net