Closed
Bug 1008629
Opened 10 years ago
Closed 10 years ago
Firefox causing excessive wakeups on OS X
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: me, Unassigned)
Details
Attachments
(1 file)
28.27 KB,
application/zip
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release) Build ID: 20140506152807 Steps to reproduce: Just have Firefox running. Actual results: After upgrading to 29 I get these messages continuously: 2014-05-10 22:03:51,000 kernel[0]: process plugin-container[80649] caught causing excessive wakeups. EXC_RESOURCE supressed due to audio playback 2014-05-10 21:20:59,000 kernel[0]: process firefox[80644] caught causing excessive wakeups. Observed wakeups rate (per sec): 166; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 471350 2014-05-10 21:00:20,000 kernel[0]: process plugin-container[80649] caught causing excessive wakeups. Observed wakeups rate (per sec): 187; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 373687 etc.
Updated•10 years ago
|
Component: Untriaged → Plug-ins
Product: Firefox → Core
Comment 1•10 years ago
|
||
These messages are triggered by a plugin that you're running. Go to Tools : Add-Ons : Plugins (in Firefox), and one-by-one, for each plugin listed, please do the following: 1) Disable the plugin. 2) Restart Firefox and check if you still see the message. Once you find it, please let us know which plugin is "at fault" here. (Note that a plugin can be loaded by an extension, so that it doesn't show up in Tools : Add-Ons : Plugins. But let's deal with that possibility later.)
For some reason it actually stopped now without me doing anything
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•