Hello list,
Has anyone else here noticed firefox consuming 15% or so of CPU time, even
while it's not supposed to be doing anything? This is version 31.5.3, with
just AdBlock Plus and YesScript added. I have remerged it and saw no
difference.
[ebuild R] www-client/firefox-31.5.3::gentoo
On 04/01/2015 07:03 AM, Peter Humphrey wrote:
> Hello list,
>
> Has anyone else here noticed firefox consuming 15% or so of CPU time, even
> while it's not supposed to be doing anything? This is version 31.5.3, with
> just AdBlock Plus and YesScript added. I have remerged it and saw no
> differ
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.
--
===
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 whe
150401 Peter Humphrey wrote:
> 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 w
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. Th
Peter Humphrey wrote:
> Hello list,
>
> Has anyone else here noticed firefox consuming 15% or so of CPU time,
> even while it's not supposed to be doing anything? This is version
> 31.5.3, with just AdBlock Plus and YesScript added. I have remerged
> it and saw no difference.
>
> [ebuild R
150401 Neil Bothwick wrote:
> On Wed, 1 Apr 2015 11:34:19 -0400, Philip Webb wrote:
>> 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?
>
On Thu, 2 Apr 2015 03:28:43 -0400, Philip Webb wrote:
> >> 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?
> > That's just b
On Thu, Apr 02, 2015 at 03:28:43AM -0400, Philip Webb wrote:
> > Do you have to kill the whole browser and not just the offending tab?
> > That's just bad programming...
>
> Do you use FF yourself ? -- if there's only 1 tab open & you kill it,
> it kills the whole FF job too.
I hate it when br
On Fri, Apr 03, 2015 at 01:02:54AM +0200, Frank Steinmetzger wrote:
> On Thu, Apr 02, 2015 at 03:28:43AM -0400, Philip Webb wrote:
>
> > > Do you have to kill the whole browser and not just the offending tab?
> > > That's just bad programming...
> >
> > Do you use FF yourself ? -- if there's only
On Thu, 2 April 2015, at 8:28 am, Philip Webb wrote:
> ...
> I've finished reading 'Guardian' (eg) & am doing something else,
> but the fan is working busily, wearing itself out & irritating me ;
> when I kill FF -- however I do it -- everything calms down.
> No, I'm not wasting my time complaini
150403 Frank Steinmetzger wrote:
> On Fri, Apr 03, 2015 at 01:02:54AM +0200, Frank Steinmetzger wrote:
>> On Thu, Apr 02, 2015 at 03:28:43AM -0400, Philip Webb wrote:
>>> if there's only 1 tab open & you kill it, it kills the whole FF job too.
>> Fortunately, we’re not left standing in the rain :
>
13 matches
Mail list logo
