Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

FX 30.0 Is it normal that after only 5 hours of use the memory is above 1.500.000 K?

  • 3 одговорa
  • 1 има овај проблем
  • 1 преглед
  • Последњи одговор послао charlotteauxfraises

more options

Hello it is all in my above question.FYI I have 12 tabs opened and my average is between 10 & 15. Before 30.0 the memory consumption was around 600-700k, but now it quickly amounts to above 1.500.000k. The crashes happens after 1.700.000 k and an automatic report is send to Mozilla.

As said I do not have too much problem with this but it is annoying as my computer slows down.

Kind regards to you all. Charlotte

Hello it is all in my above question.FYI I have 12 tabs opened and my average is between 10 & 15. Before 30.0 the memory consumption was around 600-700k, but now it quickly amounts to above 1.500.000k. The crashes happens after 1.700.000 k and an automatic report is send to Mozilla. As said I do not have too much problem with this but it is annoying as my computer slows down. Kind regards to you all. Charlotte

Изабрано решење

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

  • Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance
  • Do NOT click the Reset button on the Safe Mode start window
Прочитајте овај одговор са објашњењем 👍 1

Сви одговори (3)

more options

Reducing memory usage - Firefox

more options

Одабрано решење

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

  • Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance
  • Do NOT click the Reset button on the Safe Mode start window
more options

Thank you. Indeed in safe mode FX works fine below 150k. I will have now to identify which add-on is causing the memory problem.