Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

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

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.