From owner-freebsd-chromium@freebsd.org Sat Jul 11 11:27:00 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 67E819986BB for ; Sat, 11 Jul 2015 11:27:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D3C561DE6; Sat, 11 Jul 2015 11:26:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t6BBQsLn019093 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 11 Jul 2015 14:26:54 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t6BBQsLn019093 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t6BBQs4h019088; Sat, 11 Jul 2015 14:26:54 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 11 Jul 2015 14:26:54 +0300 From: Konstantin Belousov To: Colin Percival Cc: freebsd-chromium@freebsd.org Subject: Re: chrome processes stuck at 100% cpu [Re: svn commit: r272566 - head/sys/kern] Message-ID: <20150711112654.GC2080@kib.kiev.ua> References: <201410051736.s95Ha0U7010634@svn.freebsd.org> <55A08F18.7060803@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55A08F18.7060803@freebsd.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home 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 11:27:00 -0000 On Fri, Jul 10, 2015 at 08:35:52PM -0700, Colin Percival wrote: > The bug fixed by this commit is causing chrome processes to get stuck > spinning at 100% CPU on my FreeBSD 10.1-RELEASE laptop -- chrome is > trying to read the kern.proc.pid.# sysctl (I think in order to get the > status of a crashed rendering process) and it's going into an infinite > ERESTART loop. > > 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.