Previously when firefox went catatonic to the point that I could not even scroll, its CPU usage had gone to 100%+. Now top tells me that firefox, Web Content (with a space) or sometimes kswap... has process state D, uninterruptable sleep.
Any suggestions on how to deal?
I often have a lot of tabs open, so discovering the right one was hard enough before. Usually, it was something relatively new, so that helped. Not so much anymore. I think a lot of it is just waiting (D) for ads or running them.
Closing and reopening sometimes works, but then I have to go find all the video ads and stop them one at a time.
On 09/20/2017 01:00 PM, Michael Hennebry wrote:
Previously when firefox went catatonic to the point that I could not even scroll, its CPU usage had gone to 100%+. Now top tells me that firefox, Web Content (with a space) or sometimes kswap... has process state D, uninterruptable sleep.
Any suggestions on how to deal?
I often have a lot of tabs open, so discovering the right one was hard enough before. Usually, it was something relatively new, so that helped. Not so much anymore. I think a lot of it is just waiting (D) for ads or running them.
Closing and reopening sometimes works, but then I have to go find all the video ads and stop them one at a time.
I had that problem... and yes, it was some site's page with wild or outright broken javascript. Installed NoScript, a Firefox add-on, and using that, severely limit what javascript can run. Since then I've been good.
On Thu, 21 Sep 2017, ken wrote:
On 09/20/2017 01:00 PM, Michael Hennebry wrote:
Previously when firefox went catatonic to the point that I could not even scroll, its CPU usage had gone to 100%+. Now top tells me that firefox, Web Content (with a space) or sometimes kswap... has process state D, uninterruptable sleep.
Any suggestions on how to deal?
I had that problem... and yes, it was some site's page with wild or outright broken javascript. Installed NoScript, a Firefox add-on, and using that, severely limit what javascript can run. Since then I've been good.
From here:
https://addons.mozilla.org/en-US/firefox/addon/noscript/ ?
On 09/24/2017 02:26 AM, Michael Hennebry wrote:
On Thu, 21 Sep 2017, ken wrote:
On 09/20/2017 01:00 PM, Michael Hennebry wrote:
Previously when firefox went catatonic to the point that I could not even scroll, its CPU usage had gone to 100%+. Now top tells me that firefox, Web Content (with a space) or sometimes kswap... has process state D, uninterruptable sleep.
Any suggestions on how to deal?
I had that problem... and yes, it was some site's page with wild or outright broken javascript. Installed NoScript, a Firefox add-on, and using that, severely limit what javascript can run. Since then I've been good.
From here: https://addons.mozilla.org/en-US/firefox/addon/noscript/ ?
Yes.
It can also be accessed from within Firefox -> Tools -> Add-ons -> Extensions. Then search for it, etc.
On Wed, 27 Sep 2017, ken wrote:
On 09/24/2017 02:26 AM, Michael Hennebry wrote:
From here: https://addons.mozilla.org/en-US/firefox/addon/noscript/ ?
Yes.
It can also be accessed from within Firefox -> Tools -> Add-ons -> Extensions. Then search for it, etc.
Thanks. It works.
Michael Hennebry wrote:
On Wed, 27 Sep 2017, ken wrote:
On 09/24/2017 02:26 AM, Michael Hennebry wrote:
From here: https://addons.mozilla.org/en-US/firefox/addon/noscript/
It can also be accessed from within Firefox -> Tools -> Add-ons -> Extensions. Then search for it, etc.
Thanks. It works.
Watch out, though. My noscript just got updated this week, and it's either blocking or unblocking *everything* by default. Geez, in this webmail, I hit reply, and a popup asks me if I want to open a document of type html, and it's the hosting provider... and yet, nothing on the webmail page is blocked.
mark
On 10/04/2017 12:46 PM, Michael Hennebry wrote:
On Wed, 27 Sep 2017, ken wrote:
On 09/24/2017 02:26 AM, Michael Hennebry wrote:
From here: https://addons.mozilla.org/en-US/firefox/addon/noscript/ ?
Yes.
It can also be accessed from within Firefox -> Tools -> Add-ons -> Extensions. Then search for it, etc.
Thanks. It works.
Glad to hear it.
Unfortunately, it's quite difficult to determine which script eats up the system's resources, notably its CPU and RAM). Moreover, NoScript can only blacklist domain names, not offensive (probably defective) scripts.
NoScript, though, shouldn't take the blame for this problem. A lot of websites use javascript and use it too much. In addition, many websites use code from other sites over which they have no control. And Firefox, which is in many ways a really effective and useful browser, provides no tools (none I know of) which allows users even just to track processes launched by a visited website, let alone throttle or kill those which are causing problems. It's a serious problem which deserves a lot more attention than it's getting.
-
ken -
m.roth＠5-cent.us -
Michael Hennebry