From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id E63DB138821 for ; Wed, 1 Apr 2015 15:44:33 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 444BDE0B12; Wed, 1 Apr 2015 15:44:28 +0000 (UTC) Received: from smarthost01a.mail.zen.net.uk (smarthost01a.mail.zen.net.uk [212.23.1.1]) by pigeon.gentoo.org (Postfix) with ESMTP id 1CB5FE0B04 for ; Wed, 1 Apr 2015 15:44:26 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost01a.mail.zen.net.uk with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YdKoc-000C5T-1Q for gentoo-user@lists.gentoo.org; Wed, 01 Apr 2015 15:44:26 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Hungry firefox Date: Wed, 01 Apr 2015 16:44:25 +0100 Message-ID: <1699778.Xdgj2DgDxP@wstn> Organization: Society for Retired Gentlefolk User-Agent: KMail/4.14.3 (Linux/3.18.9-gentoo; KDE/4.14.3; x86_64; ; ) In-Reply-To: <20150401153419.GC1109@ca.inter.net> References: <9122646.azexhp1jHr@wstn> <20150401153419.GC1109@ca.inter.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost01a-IP: [82.69.80.10] X-Archives-Salt: 5869ea8f-730d-4254-b6f1-056a0f1dd52c X-Archives-Hash: 903926ad8c849991c5a832c945d5e6a4 On Wednesday 01 April 2015 11:34:19 Philip Webb wrote: > 150401 Peter Humphrey wrote: > > Has anyone else here noticed firefox consuming 15% or so of CPU time, > > even while it's not supposed to be doing anything? > > Occasionally, I've had javascripts running away with the CPU, > which stops when I kill FF & restart it. That's just bad JS programming. Thank you gents, Mention of scripts lit a lamp, so I closed the Twitter tab. CPU use went straight down to nothing. Maybe I should have a word with the Twitter devs. At any rate, I can at least poke around a bit less blindly. Thanks again, and sorry about the noise. -- Rgds Peter.