From owner-freebsd-chromium@freebsd.org Sat Jul 11 20:58:22 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 72CB3997501 for ; Sat, 11 Jul 2015 20:58:22 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FC35A57; Sat, 11 Jul 2015 20:58:22 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: by igcqs7 with SMTP id qs7so34133834igc.0; Sat, 11 Jul 2015 13:58:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=KEv0Vwt4O3Ve2cKF+czGP/IA19k8n0hPj3dcNKv33Us=; b=xRZ2UPEgJXGW5j8HDOfALZWrPyzVIIE4hNFOtMuz3dYKycVtanOdX+d2ROQtDmTj+h Dgb9/gLLFbeIdyTuS7liLBe3nS/jsaZok3T1c2g+OKGpLvzfOYWp5eYMg/qsF81Qwl+7 eQ3oaNMt3vIipV5q0nTr0lWwfAHWdkrayOWXZsjfGOdsgovClpG/h4Gy/L7W8oCBQqQ8 bnS3BtHaWAP3mh5f/GUrJVTj9sp0T328eSH4rI7ZuLcGaYZXmTbj6MgrGy1lLDV4pj/Q HkpYP4CFI5N2u9GTy1rFZ3JdMyefyZiXgL5PO+YaNvAgkHfWDocuLiOeMYrY7YfQph3n m3+w== X-Received: by 10.50.143.101 with SMTP id sd5mr5277726igb.44.1436648301689; Sat, 11 Jul 2015 13:58:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.240.146 with HTTP; Sat, 11 Jul 2015 13:57:42 -0700 (PDT) In-Reply-To: <55A17EAC.1000604@freebsd.org> References: <201410051736.s95Ha0U7010634@svn.freebsd.org> <55A08F18.7060803@freebsd.org> <20150711112654.GC2080@kib.kiev.ua> <55A17EAC.1000604@freebsd.org> From: Miguel C Date: Sat, 11 Jul 2015 21:57:42 +0100 Message-ID: Subject: Re: chrome processes stuck at 100% cpu [Re: svn commit: r272566 - head/sys/kern] To: Colin Percival Cc: Konstantin Belousov , chromium-list freebsd Content-Type: text/plain; charset=UTF-8 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:58:22 -0000 I am at least :| Was just using chrome and wondering WT...H was wrong and just saw the email. If important: FreeBSD r2d2 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r285207+284d3e5(master) --> chromium-43.0.2357.130 Not sure what triggers it... happens randomly opening new tabs from links (new empty tab seems to work fine all the time) :| Melhores Cumprimentos // Best Regards ----------------------------------------------- Miguel Clara IT - Sys Admin & Developer On Sat, Jul 11, 2015 at 9:38 PM, Colin Percival wrote: > 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 > _______________________________________________ > freebsd-chromium@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.org"