Mozilla 도움말 검색

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

자세히 살펴보기

Memory usage is worse than ever (58.0.1 64-bit)

  • 4 답장
  • 2 이 문제를 만남
  • 3 보기
  • 최종 답변자: rwmol

more options

I run Windows 7 with 6 GB. Running approx. 40 tabs, Firefox is using about 4 GB and 7 processes just a minute or so after startup! This is completely unacceptable, and much worse than pre-Quantum Firefox. Googling, addons to show memory usage per tab from a year or two back no longer work. ???

I run Windows 7 with 6 GB. Running approx. 40 tabs, Firefox is using about 4 GB and 7 processes just a minute or so after startup! This is completely unacceptable, and much worse than pre-Quantum Firefox. Googling, addons to show memory usage per tab from a year or two back no longer work. ???

모든 댓글 (4)

more options

As program is almost rewritten it will take time to fix. I will be better with updates.

more options

There needs to be a way for the user to specify a maxMemoryUsage setting.

more options

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

  • switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Appearance
  • do NOT click the "Refresh Firefox" button on the Safe Mode start window

You can try to modify multi-process settings to see if this has effect.

  • set number of content processes to 1 if it is currently set to a higher value (4)
    Options/Preferences -> General -> Performance
    remove checkmark: [ ] "Use recommended performance settings"

Note that the multi-process opt-in pref browser.tabs.remote.autostart.2 is no longer used in Firefox 58+. In Firefox 58+ only browser.tabs.remote.autostart is used, so you need to set this pref to false to disable multi-process.

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

more options

There has to be some way to fix this: