Thanks to a tough moderator and thanks to other contributors in this thread, I found the solution as to why iceweasel was eating too many CPU cycles. The issue is firefox related, and has been reported as a bug.
Quote:
|
The problem lies in CSS3 animations. There’s a bug in Iceweasel that makes it refresh the page even when nothing is changing whenever there’s a animation property set to an element even when the element is hidden. See https://bugzilla.mozilla.org/show_bug.cgi?id=962594.
|
The solution is to edit the userContent.css file adding the following lines:
Code:
@-moz-document domain(facebook.com) {
* {
-moz-animation: none !important;
animation: none !important;
}
}
Thank goodness, the issue was not security related.
