From owner-freebsd-chromium@freebsd.org Sat Jul 11 20:39:07 2015 Return-Path: Delivered-To: freebsd-chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E97739970DA for ; Sat, 11 Jul 2015 20:39:07 +0000 (UTC) (envelope-from bounces+73574-e33c-freebsd-chromium=freebsd.org@sendgrid.net) Received: from o1.l99.sendgrid.net (o1.l99.sendgrid.net [198.37.153.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9C47EB4 for ; Sat, 11 Jul 2015 20:39:07 +0000 (UTC) (envelope-from bounces+73574-e33c-freebsd-chromium=freebsd.org@sendgrid.net) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=Tl2VNp3WGzJ27ZP7RJZAhuetWBQ=; b=wcK+wk82oFE5/EFYfV EXM+CZxEdPFy0EO8A7vNO6kE4tBBuMc1uypr+fgk3I1WliFrssB+b7VMsh6s38j9 C/sSslJphdplnJ+qe7MJdj36NuPB7WXjoo7BbdVU0N7GMJWXtLRqZLiNrj3anFSW 7H8g0Victa+gQE1pk4L1I7sCM= Received: by filter0487p1mdw1.sendgrid.net with SMTP id filter0487p1mdw1.30193.55A17EE96 2015-07-11 20:39:05.27441479 +0000 UTC Received: from mail.tarsnap.com (ec2-54-86-246-204.compute-1.amazonaws.com [54.86.246.204]) by ismtpd-015 (SG) with ESMTP id 14e7ed7beb1.17f0.68318 for ; Sat, 11 Jul 2015 20:39:05 +0000 (UTC) Received: (qmail 75358 invoked from network); 11 Jul 2015 20:35:21 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 11 Jul 2015 20:35:21 -0000 Received: (qmail 63663 invoked from network); 11 Jul 2015 20:38:04 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 11 Jul 2015 20:38:04 -0000 Message-ID: <55A17EAC.1000604@freebsd.org> Date: Sat, 11 Jul 2015 13:38:04 -0700 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Konstantin Belousov CC: freebsd-chromium@freebsd.org Subject: Re: chrome processes stuck at 100% cpu [Re: svn commit: r272566 - head/sys/kern] References: <201410051736.s95Ha0U7010634@svn.freebsd.org> <55A08F18.7060803@freebsd.org> <20150711112654.GC2080@kib.kiev.ua> In-Reply-To: <20150711112654.GC2080@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SG-EID: XhyBwObMhraAR+zdwMupjVGEs/UG/hkvmklqQBd8XaaHnRZel/ukO99ClrfA/k7XDdn+uCrw6wRbrz ONP40jVmFbe2gEbiksL5l1zf0OrYJMfwmwtRyn+Djx51houewYfviAu9/t6sr1N8gYrQItIH5UxDb7 sioXe6W3aR/0oEKYj0PTB09hSEhVhgd/XowU X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jul 2015 20:39:08 -0000 On 07/11/15 04:26, Konstantin Belousov wrote: > On Fri, Jul 10, 2015 at 08:35:52PM -0700, Colin Percival wrote: >> Is anyone else seeing the 100%-CPU-usage chrome problem? It seems to >> be triggered by a crashing chrome rendering process, and I don't know >> what's causing that, so it's possible that this isn't affecting many >> other people. >> >> Konstantin, if this turns out to be affecting a lot of people, do you >> think we could get an errata notice for this? > > I would not strongly object against EN, but this is underqualified > bug for the releng branch, IMO. The issue does not affect the system > integrity, since the looping process must be killable. > > If secteam agrees to spent the time on this, why not ? But IMO it inflates > the meaning of the releng branch. For the 'new suport model', this > would have clean resolution, but for 10.x I am not sure what to do. The definition of "errata" was always largely based on whether there was a significant impact to users, which is why I was asking if anyone else was seeing this problem -- if I'm the only person, it definitely doesn't deserve an EN, but if *everybody* using Chrome is running into this I think it might make sense even though the impact on any one user is only at the level of annoyance. Nobody else seems to be chiming in to say that they're affected by this bug yet though... -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid