Цей вебсайт матиме обмежену функціональність, доки ми проводимо його обслуговування для поліпшення роботи. Якщо прочитана стаття не розв'язала вашу проблему і ви хочете поставити питання, наша спільнота підтримки з радістю допоможе вам на @FirefoxSupport у Twitter та /r/firefox на Reddit.

Avatar for Username

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Firefox still uses too much RAM, memory leak issue has not been fixed

  • 6 відповідей
  • 3 мають цю проблему
  • 29 переглядів
  • Остання відповідь від ThePillenwerfer

VGNerd
VGNerd
more options

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.

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)

VGNerd
VGNerd Власник питання
more options

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.

Корисно?

PavelkoT
PavelkoT
more options

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?

Корисно?

VGNerd
VGNerd Власник питання
more options

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.

Корисно?

Paul
Paul
  • Moderator
  • Top 10 Contributor
more options

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.

  1. 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.
  2. 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.)

Fx115aboutcrashes

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

Корисно?

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

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

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.

Корисно?

ThePillenwerfer
ThePillenwerfer
more options

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.

Корисно?

Запитати

Щоб відповідати на повідомлення, ви повинні ввійти у свій обліковий запис. Поставте нове питання, якщо ви ще не маєте облікового запису.