From owner-freebsd-chromium@freebsd.org Mon Jul 13 10:26:04 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 E8D16999602 for ; Mon, 13 Jul 2015 10:26:04 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from smtp.rlwinm.de (smtp.rlwinm.de [IPv6:2a01:4f8:201:31ef::e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B068A14B8 for ; Mon, 13 Jul 2015 10:26:04 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from m4800.rlwinm.de (unknown [87.253.189.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.rlwinm.de (Postfix) with ESMTPSA id E6CDCF178 for ; Mon, 13 Jul 2015 12:25:52 +0200 (CEST) Message-ID: <55A39234.1040700@rlwinm.de> Date: Mon, 13 Jul 2015 12:25:56 +0200 From: Crest User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: 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> <55A17EAC.1000604@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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: Mon, 13 Jul 2015 10:26:05 -0000 On 11.07.2015 22:57, Miguel C wrote: > I am at least :| You're not alone. All my FreeBSD 10.1p14/amd64 boxes are affected and this bug forced me to move from chromium to firefox until it's fixed.