From owner-freebsd-chromium@FreeBSD.ORG Mon May 14 11:06:38 2012 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C3E89106564A for ; Mon, 14 May 2012 11:06:38 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 945E78FC17 for ; Mon, 14 May 2012 11:06:38 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q4EB6c2f052808 for ; Mon, 14 May 2012 11:06:38 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q4EB6bbP052804 for chromium@FreeBSD.org; Mon, 14 May 2012 11:06:37 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 May 2012 11:06:37 GMT Message-Id: <201205141106.q4EB6bbP052804@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: chromium@FreeBSD.org Cc: Subject: Current problem reports assigned to chromium@FreeBSD.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2012 11:06:38 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/165637 chromium www/chromium: 17.0.963.56 fails to find some ns plugin o ports/165636 chromium www/chromium: 17.0.963.56: unable to import data from o ports/165635 chromium www/chromium: 17.0.963.56: proxy isn't read by chrome f ports/165634 chromium www/chromium : 17.0.963.56 doesn't show physical print 4 problems total. From owner-freebsd-chromium@FreeBSD.ORG Thu May 17 06:16:08 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3CEA1065674; Thu, 17 May 2012 06:16:07 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo103.cox.net (eastrmfepo103.cox.net [68.230.241.215]) by mx1.freebsd.org (Postfix) with ESMTP id 74D7C8FC17; Thu, 17 May 2012 06:16:07 +0000 (UTC) Received: from eastrmimpo306.cox.net ([68.230.241.238]) by eastrmfepo103.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20120517061601.TXGP8874.eastrmfepo103.cox.net@eastrmimpo306.cox.net>; Thu, 17 May 2012 02:16:01 -0400 Received: from serene.no-ip.org ([98.164.83.188]) by eastrmimpo306.cox.net with bizsmtp id AuG01j00A43nm9e02uG1AJ; Thu, 17 May 2012 02:16:01 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020207.4FB497A1.0032,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=oNsJgJ5cAGpTaXJztO+k5aVuruDCBvmbzOAslSMJ7bY= c=1 sm=1 a=7qPX-ydv6MoA:10 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=F4D4Y6gUi4XSUMrqnG4xkg==:17 a=kviXuzpPAAAA:8 a=nwSUVsnSYRXeURJCeeMA:9 a=CjuIK1q_8ugA: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 q4H6FxbZ014581; Thu, 17 May 2012 01:16:00 -0500 (CDT) (envelope-from conrads@cox.net) Date: Thu, 17 May 2012 01:15:54 -0500 From: "Conrad J. Sabatier" To: freebsd-chromium@freebsd.org Message-ID: <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-current@freebsd.org Subject: Chrome crashing system (amd64-10.0-CURRENT) X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2012 06:16:08 -0000 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 make matters worse, no trace of what's happening is anywhere to be found. Nothing in any log files. The system doesn't drop into the kernel debugger, either. It's either a hard freeze or sudden reboot. I've tried rebuilding the chromium port, with both clang and gcc 4.6, to no avail. I've also updated the system sources several times this week and remade world/kernel. Nothing seems to help. I'm totally stumped as to how to determine what's going on here. Any suggestions as to how to obtain some useful info? Thanks! -- Conrad J. Sabatier conrads@cox.net From owner-freebsd-chromium@FreeBSD.ORG Thu May 17 07:15:50 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 877EE1065670; Thu, 17 May 2012 07:15:50 +0000 (UTC) (envelope-from john@ixsystems.com) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) by mx1.freebsd.org (Postfix) with ESMTP id 68DCE8FC20; Thu, 17 May 2012 07:15:49 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.iXsystems.com (Postfix) with ESMTP id 6190C1C43; Thu, 17 May 2012 00:15:48 -0700 (PDT) Received: from mail.iXsystems.com ([127.0.0.1]) by localhost (mail.ixsystems.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 75803-04-4; Thu, 17 May 2012 00:15:40 -0700 (PDT) Received: from thinkbsd.divinix.org (unknown [10.8.0.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id C75C81C28; Thu, 17 May 2012 00:11:43 -0700 (PDT) Date: Thu, 17 May 2012 00:11:42 -0700 From: John Hixson To: "Conrad J. Sabatier" Message-ID: <20120517071141.GL2701@thinkbsd.divinix.org> References: <20120517011554.5d16067e@serene.no-ip.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120517011554.5d16067e@serene.no-ip.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-chromium@freebsd.org, freebsd-current@freebsd.org Subject: Re: Chrome crashing system (amd64-10.0-CURRENT) X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2012 07:15:50 -0000 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 make matters worse, no trace of what's happening is anywhere to be > found. Nothing in any log files. The system doesn't drop into the > kernel debugger, either. It's either a hard freeze or sudden reboot. > > I've tried rebuilding the chromium port, with both clang and gcc 4.6, > to no avail. I've also updated the system sources several times this > week and remade world/kernel. Nothing seems to help. > > I'm totally stumped as to how to determine what's going on here. Any > suggestions as to how to obtain some useful info? > To add to this, I've had the same problem on 10-CURRENT for several months now. -John From owner-freebsd-chromium@FreeBSD.ORG Thu May 17 15:55:51 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00AF21065673 for ; Thu, 17 May 2012 15:55:51 +0000 (UTC) (envelope-from evanm@google.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9C9218FC08 for ; Thu, 17 May 2012 15:55:50 +0000 (UTC) Received: by yenl8 with SMTP id l8so2438074yen.13 for ; Thu, 17 May 2012 08:55:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-system-of-record; bh=Jq9sS4phQMpUx+Yf9kxsBqJiYU93L+te6GTn2UbMUFA=; b=Pjmjn4umC2UFhvhDDonawrZ4fSVx3ddr5WUUPUiKONZcmesvRu592rG4pZC/kHSQXE zmeiQ+Lr9Z2gA3WCg63g+P7gZ02kqOaz85S9v3LmaO7F6O1rORKfb+kaa5AwJdNOKK3k rV60nleadwqTznGFGCa4+R83jLVa7+dMUcefuPGHIMTNvs1ovyi5g/CJduXsTzSwCdLy wgcGwZ7NGFHCvxgb3FzDGcWb6VO/GiSF2XnSO4qR/j7/RZNqHAMbfu9yRtw+BVmnA3o2 2Au1urcK6clazG3VSU+uTi0YPTjLd6Y/5Vpy5f6JDi73ugJzrYqa649sOEVB07Bjmme6 GNMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-system-of-record:x-gm-message-state; bh=Jq9sS4phQMpUx+Yf9kxsBqJiYU93L+te6GTn2UbMUFA=; b=YChw1RjCfitM8Gs2UjkbByojhqtf6BXO6BMy2Of2QLdR4lVXIbNfWIx6CTNofkQFsq ToJElp/sHwTt/yFE0N3vzt/CxxKobb461tJQZj30KwsKAV4DnlJ3IOBzTjcE7l8cOd0j 4EjJrGNuJyWezuXZ/MpsyRsrHIlYQv+iYNYI6RGtSvrAPSELi0FvJhVnlD5JHbSSeX5Q Z2Z/tS56bSBolwpU888I5rXJkv3BiC/ZKLd8ls3OpolAmrk5ibn/cvq8h/4zvgjJjpMM XXth15OwX8b9wpINjrzNbIe7irOw4GjG9YavQCJ3d0T5M9qA4zWCotoexG+bjDw3RG2Y bwRg== Received: by 10.236.114.161 with SMTP id c21mr8711197yhh.51.1337270150157; Thu, 17 May 2012 08:55:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.114.161 with SMTP id c21mr8711163yhh.51.1337270149848; Thu, 17 May 2012 08:55:49 -0700 (PDT) Sender: evanm@google.com Received: by 10.101.156.21 with HTTP; Thu, 17 May 2012 08:55:49 -0700 (PDT) In-Reply-To: <20120517011554.5d16067e@serene.no-ip.org> References: <20120517011554.5d16067e@serene.no-ip.org> Date: Thu, 17 May 2012 08:55:49 -0700 X-Google-Sender-Auth: XfLA5WyS5Ad7RuYOFBeleNv3m6o Message-ID: From: Evan Martin To: "Conrad J. Sabatier" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true X-Gm-Message-State: ALoCoQljZble6fvU4jAMNYrdM6318fm8h2HDTfsDYx+6ralvSiD/8ZHXBZhxo8OcJgUPu2zEb8zAxHgeEGVfPoiMiTkV4GCwjeZQw2bQDUUSGXW0JqPIw8RX1iG7AdtnRQD+UgfHN67+WdxkllMvWU1blLUNVFA2xA== Cc: freebsd-chromium@freebsd.org, freebsd-current@freebsd.org Subject: Re: Chrome crashing system (amd64-10.0-CURRENT) X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2012 15:55:51 -0000 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. On Wed, May 16, 2012 at 11:15 PM, Conrad J. Sabatier wrot= e: > For the last week or so, I've been unable to run chrome. =A0Any attempt > to start it up will cause the system either to freeze up or reboot. > > To make matters worse, no trace of what's happening is anywhere to be > found. =A0Nothing in any log files. =A0The system doesn't drop into the > kernel debugger, either. =A0It's either a hard freeze or sudden reboot. > > I've tried rebuilding the chromium port, with both clang and gcc 4.6, > to no avail. =A0I've also updated the system sources several times this > week and remade world/kernel. =A0Nothing seems to help. > > I'm totally stumped as to how to determine what's going on here. =A0Any > suggestions as to how to obtain some useful info? > > Thanks! > > -- > Conrad J. Sabatier > conrads@cox.net > _______________________________________________ > freebsd-chromium@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.or= g" From owner-freebsd-chromium@FreeBSD.ORG Thu May 17 23:08:57 2012 Return-Path: Delivered-To: freebsd-chromium@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-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues 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 From owner-freebsd-chromium@FreeBSD.ORG Thu May 17 23:12:16 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3C4D61065674 for ; Thu, 17 May 2012 23:12:16 +0000 (UTC) (envelope-from evanm@google.com) Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id D52A98FC18 for ; Thu, 17 May 2012 23:12:15 +0000 (UTC) Received: by ggnm2 with SMTP id m2so2986369ggn.13 for ; Thu, 17 May 2012 16:12:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-system-of-record; bh=ghFcL8uwcfxfnYgafDq++zBcoq3yJSuSPW8IPkKE09Y=; b=BDi4BymwBruY31EE7FYpsimhqSKk+8MW3AHf2pq9v0rrB/0xnKUmaxgPShBLd7SiDQ 8u55lw144GnvgZOwrMC2ntoLWTgiTuIo1rB61BhvPXYBgR49o3+v2B+AIOA1bQhL9X6A 2l3R9kjhuHA0hS6B3xwUMBSKAqWvfRjvuI2KY64RXK50mt0nE9X+pWlmG240/LGxPDGn Rr+wmnqGWnSHhr7YNZg9IzP4JmhOvQThTDeSrOmZrhI9aWZFO7vyKaSAY5efqPA/ta7e WR9KO7PgNz0IBuqFsQJbhTQyPLyd3GnwVRNX7dbOWM2nMuR8VjP55r/TlpojINNLktNw ytWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-system-of-record:x-gm-message-state; bh=ghFcL8uwcfxfnYgafDq++zBcoq3yJSuSPW8IPkKE09Y=; b=N7VvrFolHAGXZ96MxFi9GaqCJkcobV3bpWyDWnVH3Ab6MAwgizdKPZBVw21xwE5x0p rT33ot6AznqgTVxquuZLHZGFlKcUSNApS6vqGSOCUyPpRTcOeCiS3dUfoHbeSGEAHngz LIWqx4uwY2MBImKJum2iWyOx6fGTBVzVF+pWqilQP65gOUQA7D3HpSQexPdjD1wXUTVV B7ukwTXgtQa35k9PNycUV1Ke/VW8xBqlGDgjbURYtEIkkG/7aQAwRIAF33EAiB4sLr3P gw5EuENtQvPo3BpbKtbnXgwZUm2IHx8dYECc/B4glBs2L+qxyxjsFJXJiYaojgmOfwgg wG2g== Received: by 10.236.126.15 with SMTP id a15mr10103689yhi.14.1337296335222; Thu, 17 May 2012 16:12:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.126.15 with SMTP id a15mr10103679yhi.14.1337296335103; Thu, 17 May 2012 16:12:15 -0700 (PDT) Sender: evanm@google.com Received: by 10.101.156.21 with HTTP; Thu, 17 May 2012 16:12:15 -0700 (PDT) In-Reply-To: <20120517180849.72ac2664@serene.no-ip.org> References: <20120517011554.5d16067e@serene.no-ip.org> <20120517180849.72ac2664@serene.no-ip.org> Date: Thu, 17 May 2012 16:12:15 -0700 X-Google-Sender-Auth: yAEkk2mRFav6kIXxnbTa-cj8oHY Message-ID: From: Evan Martin To: "Conrad J. Sabatier" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true X-Gm-Message-State: ALoCoQntS/uYtQtLU/yWxO7k5WuPT3cuu2sWdvcxoAZrsaZpe1monW6lNPTuP8m5rONNQIv8CD5TK312KoUu/mEdYg92kAAgM+wLZlMGB33H3PlUQ1OwnJ6GQILU+v5tSRrryv0Sw82toWgtPzXV0ZVjJ8aoUVGayw== Cc: freebsd-chromium@freebsd.org, John Hixson , freebsd-current@freebsd.org Subject: Re: Chrome crashing system (amd64-10.0-CURRENT) X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2012 23:12:16 -0000 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. 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. From owner-freebsd-chromium@FreeBSD.ORG Thu May 17 23:26:45 2012 Return-Path: Delivered-To: freebsd-chromium@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-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues 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 From owner-freebsd-chromium@FreeBSD.ORG Fri May 18 08:45:51 2012 Return-Path: Delivered-To: freebsd-chromium@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: freebsd-chromium@freebsd.org, John Hixson , freebsd-current@freebsd.org Subject: Re: Chrome crashing system (amd64-10.0-CURRENT) X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues 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