Firefox still uses too much RAM, memory leak issue has not been fixed
I'm really shocked that the developers at Firefox has not at all fixed the memory leak issue, which caused my PC to crash three times in a row. This is clearly unacceptable; even other browsers I use don't eat up a lot of RAM in a matter of seconds that ends up my PC lagging, or worse, crashing as a result. To the Firefox devs; why are you overlooking an ongoing issue that should've been easily fixed from the get-go, especially with updates that obviously have nothing to do with the memory leak issue? It's really easy to make such a popular browser not hog up memory so easily without causing so much lag, even on higher end PCs.
If the memory leak issue isn't fully resolved by greatly reducing memory usage, especially if I'm only using one or two tabs with me, I will have to consider seeking for another working browser that does not have a memory leak issue, and remove Firefox and never reinstall it altogether.
Всички отговори (6)
And no, Chrome isn't any better, and Safari basically bailed Windows, and I don't even have a MacOS either. Chrome is also trying to remove AdBlock extensions altogether, just to make the browser much more user-hostile because of their obsession with ads. And Firefox still has a memory issue that has not been addressed because of poor developer decision. These big browsers like Firefox are definitely falling from grace.
Websites use Javascript. Javascript code is code which runs on your machine. So these websites consumes more resources of your machine. How many RAM your machine has? What website loads your machine?
16 GB of RAM, which isn't supposed to be a lot, but Firefox continues to use up more RAM in seconds, which is still unacceptable. Is there really no way to minimize Firefox from using up too much RAM when it's not supposed to? Or is Firefox basically meeting its inevitable end? Because I'm sure not all browsers consume THAT much RAM, much less in a matter of seconds which can cause my PC to unexpectedly lag and then crash altogether.
Hi
I run Firefox perfectly fine on a device with half that level for RAM. Webpages open fine, video plays okay and there no crashes.
In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.
The crash report is several pages of data. We need the report numbers to see the whole report.
- Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted (and Unsubmitted, if any) Crash Reports will appear, similar to the one shown below.
- Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.
Note: If a recent Report ID does not start with bp- click on it to submit the report.
(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)
Thank you for your help!
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
Start Firefox in Troubleshoot Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration or if userChrome.css/userContent.css is causing the problem.
- switch to the Default System theme: "3-bar" menu button or Tools -> Add-ons -> Themes
- do NOT click "Refresh Firefox" in the Troubleshoot Mode start window
- https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode
- https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems
You can check the about:memory and about:processes pages for info about all processes. See also the about:unloads page for info about the tabs.
None of my computers have more than 4GB RAM and all work fine with Firefox, in fact I've never found it inadequate for anything.
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.