Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Firefox using a lot or memory

  • 3 wótegrona
  • 1 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót cor-el

more options

With ONE Firefox window open is it normal to have this many (12) show up in Task Manager (see attachment) and using so much RAM??

With ONE Firefox window open is it normal to have this many (12) show up in Task Manager (see attachment) and using so much RAM??
Pśipowjesone fota wobrazowki

Wubrane rozwězanje

It is quite normal to see more Firefox processes running.

  • process for the main Firefox thread (user interface)
  • one or more content processes
    you see more content processes when Fission is enabled
  • process for the compositor thread
  • process for extensions
  • process for WebRender when this feature is enabled

There are several toolkit.aboutProcesses prefs on the about:config page to show more info. You can find the current multi-process state on the Troubleshooting Information page (about:support).

  • "Help -> Troubleshooting Information"
    "Application Basics":<be>Multiprocess Windows and Fission Windows
    "Remote Processes" (Web Content)

See also the about:memory and about:processes pages for more information about all processes.

Toś to wótegrono w konteksće cytaś 👍 1

Wšykne wótegrona (3)

more options

donthavecow said

Did you restart and launch FireFox again to see what happens.

Yes, this it's the same. This is the "norm" for a long time - I just finally trying to find out why.

more options

It is quite normal to see more Firefox processes running.

  • process for the main Firefox thread (user interface)
  • one or more content processes
    you see more content processes when Fission is enabled
  • process for the compositor thread
  • process for extensions
  • process for WebRender when this feature is enabled

There are several toolkit.aboutProcesses prefs on the about:config page to show more info. You can find the current multi-process state on the Troubleshooting Information page (about:support).

See also the about:memory and about:processes pages for more information about all processes.

  • you can open "about:" pages via the location/address bar
    this "about:" protocol is used to access special pages

Wót cor-el změnjony

more options

Wubrane rozwězanje

It is quite normal to see more Firefox processes running.

  • process for the main Firefox thread (user interface)
  • one or more content processes
    you see more content processes when Fission is enabled
  • process for the compositor thread
  • process for extensions
  • process for WebRender when this feature is enabled

There are several toolkit.aboutProcesses prefs on the about:config page to show more info. You can find the current multi-process state on the Troubleshooting Information page (about:support).

  • "Help -> Troubleshooting Information"
    "Application Basics":<be>Multiprocess Windows and Fission Windows
    "Remote Processes" (Web Content)

See also the about:memory and about:processes pages for more information about all processes.