ค้นหาฝ่ายสนับสนุน

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

100%+ CPU FIREFOX HOG FOUND

  • 7 การตอบกลับ
  • 5 คนมีปัญหานี้
  • 2 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย zoneout

more options

Many users have complained about cpu spiking to 100% and flat-lining on FF for years. They run in safe mode and disable plugins all to no avail.

Well I have been going thru the same gyrations and I finally believe I know what the probable cause is. Javascript. I downloaded NoScript to block Javascript but of course almost every website nowadays needs javascript to run - else you get either a blank screen or some 1995-ish looking HTML page.

For example on an ebay page which is heavily javascript my cpu spikes to 100% every time I reload the page.

Mind you I have the latest version of java so please dont suggest I update. I am stuck on FF 49 because later versions have a problem with certain iMacros commands. However this problem impacts all versions of FF for years so it has not ever been fixed and changing versions makes no difference.

So what is the answer? Nothing we can do I suspect. The interface between javascript and Firefox needs to be optimized by the developers - if it is even possible. If somebody knows of a magical internal switch that we can toggle to improve performance in this regard I am all ears.

Many users have complained about cpu spiking to 100% and flat-lining on FF for years. They run in safe mode and disable plugins all to no avail. Well I have been going thru the same gyrations and I finally believe I know what the probable cause is. Javascript. I downloaded NoScript to block Javascript but of course almost every website nowadays needs javascript to run - else you get either a blank screen or some 1995-ish looking HTML page. For example on an ebay page which is heavily javascript my cpu spikes to 100% every time I reload the page. Mind you I have the latest version of java so please dont suggest I update. I am stuck on FF 49 because later versions have a problem with certain iMacros commands. However this problem impacts all versions of FF for years so it has not ever been fixed and changing versions makes no difference. So what is the answer? Nothing we can do I suspect. The interface between javascript and Firefox needs to be optimized by the developers - if it is even possible. If somebody knows of a magical internal switch that we can toggle to improve performance in this regard I am all ears.

การตอบกลับทั้งหมด (7)

more options

JavaScript has nothing to with Java. http://kb.mozillazine.org/JavaScript_is_not_Java http://kb.mozillazine.org/Java http://kb.mozillazine.org/JavaScript

NoScript is an excellent add-on, but learning to use it effectively will take some time. To begin with, NoScript is not "all or nothing"; in the beginning users will need to selectively enable JavaScript domain-by-domain for each website they visit. NoScript will "remember" those "allow" settings for the next the user visits the website. That will take some time for new users of NoScript for there most visited websites, but it will never end for "new" websites that are visited.

I have been using NoScript for >10 years now, and with the increased use of JavaScript on webpages, along with the increased number of each different domains that the "average webpage" connects to - I wonder if I would have the patience to even learn to use NoScript these days. In the mid-00's the "average website" might connect to 5 or 6 different domains; now-a-days it seems to be like 25-plus domains appearing in NoScript, that the user can "whitelist" to allow JavaScript for that domain.

To get started users need to become familiar with the features in NoScript. https://noscript.net/features And see the Frequently Asked Questions support page: https://noscript.net/faq

Finally, NoScript has its own support forum over here: https://forums.informaction.com/viewforum.php?f=3 The support contributors over there probably have their own "tips & tricks" getting started as a new user of NoScript.

Plus, blocking JavaScript is just a small part of what NoScript actually does. I really like the Anti-XXS feature - (cross-site scripting) and the ABE feature - (Application Boundaries Enforcer).

more options

Also, unless you are planning on getting a new PC or installing a more modern operating system, learning about how to use NoScript might be a waste of time for you. Mozilla is dropping support for Windows Vista in a few months in new releases - March 2017. Existing users will automatically get the ESR version, which will get security updates into 2018. https://blog.mozilla.org/futurereleases/2016/12/23/firefox-support-for-xp-and-vista/ https://support.mozilla.org/en-US/kb/end-support-windows-xp-and-vista

more options

Not sure what your point is. Firefox has a problem running java efficiently. Go to any site that is java and refresh the screen FF will spike the CPU while the scripts complete. Some scripts hang and that is when FF will eat your memory and CPU forcing a restart.

As for FF dropping support for VISTA doesnt`t really matter. The problem exists independent of the OS platform. If you are not familiar with the issue just google Firefox high CPU.

more options

Just tried to help you solve your problems with JavaScript your attempt to use the NoScript extension, along with pointing out your confusion over Java vs. JavaScript. Yes, Java can be a real hog - but that's nothing new. I have had problems with Java using too many resources since 2000 or 2001, long before Firefox was a "gleam in the eyes" of the Mozilla developers.

I am fully aware of the perceived faults with Firefox and supposed CPU problems, most of which are solvable. No need for me to search for complaints, as mostly those postings are from users who aren't interested in learning how to diagnose and solve their problems, just "blowing off steam" in most cases. Personally, I have never encountered 100% CPU usage that I couldn't easily pinpoint and easily fix.

If your point in posting here was to express your displeasure with Firefox, you should provide feedback to Mozilla here: https://input.mozilla.org/en-US/feedback

more options

Java in itself isn`t a hog. Firefox is inefficient in handling it. Every other browser out there the CPU will hardly show a blip when loading java - as has been noted - Firefox spikes to 100% loading java. If enough java tabs are loaded the fan in my laptop starts to sound like a drone.

Thanks for the link to the developers but it is impossible that they are unaware of this issue. It has been going on for years.

more options

Give us examples of sites that Firefox is having issues with while running the Java Plugin from Oracle in Firefox. eBay for example does not need the Java Plugin.

As stated the separate Java Plugin has no relation to the JavaScript in Firefox. JavaScript was originally going to be called LiveScript. The LiveScript name would have reduced the confusion substantially over the years but they wanted to get on popularity of the Java Plugin back then.

http://kb.mozillazine.org/JavaScript_is_not_Java

เปลี่ยนแปลงโดย James เมื่อ

more options

Java script is the issue not Oracle java. Sorry for the confusion. When java script is blocked in noscript then ebay pages do not load. I have posted a video as you requested here https://www.mediafire.com/?8an0a0h8y0p9y91 since this site does not allow it for whatever reason.

You will note that when the ebay page is refreshed Norton will pop a warning about firefox hogging ram. You will also note that the CPU graph is flat-lined at 100%. Firefox itself would be 90%+ during this time but the video capture app needs some CPU so FF is grabbing whatever is available (generally 50%+) and slow page load.

Additionally, at various times I will get nonresponsive script dialogs asking if I want to let the script continue or abort. So this is definitely an issue with the script interpreter.