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 A7069138821 for ; Wed, 1 Apr 2015 20:48:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 81E97E092E; Wed, 1 Apr 2015 20:48:18 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7866BE086E for ; Wed, 1 Apr 2015 20:48:17 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YdPYc-0007P6-45 for gentoo-user@lists.gentoo.org; Wed, 01 Apr 2015 22:48:14 +0200 Received: from 67-130-15-94.dia.static.qwest.net ([67.130.15.94]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Apr 2015 22:48:14 +0200 Received: from grant.b.edwards by 67-130-15-94.dia.static.qwest.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Apr 2015 22:48:14 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Grant Edwards Subject: [gentoo-user] Re: Hungry firefox Date: Wed, 1 Apr 2015 20:48:07 +0000 (UTC) Message-ID: References: <9122646.azexhp1jHr@wstn> <20150401153419.GC1109@ca.inter.net> <20150401173000.7ad251d3@hactar.digimed.co.uk> X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 67-130-15-94.dia.static.qwest.net User-Agent: slrn/1.0.1 (Linux) 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 X-Archives-Salt: 953f28f0-9065-40d6-838a-b4c931fc9e54 X-Archives-Hash: a34a27ffecda36e950d4641efdd68d14 On 2015-04-01, Neil Bothwick wrote: > On Wed, 1 Apr 2015 11:34:19 -0400, Philip Webb 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. > > Do you have to kill the whole browser and not just the offending tab? Just the offending tab _should_ do it. > That's just bad programming... Probably. From what I've seen, the web is build almost entirely out on "bad programming". I'm not sure it's even possible to do good programming in PHP, though you can in JavaScript. -- Grant Edwards grant.b.edwards Yow! Why is it that when at you DIE, you can't take gmail.com your HOME ENTERTAINMENT CENTER with you??