Firefox: Process and system related issues
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: mcgiwer, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0
Steps to reproduce:
Open Firefox and yask manager (prefered ones: ProcessExplorer or Process Hacker) to see the Firefox processess
Actual results:
-
it has a too big working set and system resources usage
-
firefox opens too many unnessecary and unknown internet connections by default
-
it opens too many sub-processess (it should open one main and a one new sub-process for each open tab/window). Instead of that, it opens many unknown processess and there is not listed in the task manager, with one is to with
Above can create security and DoS risks (system may get out of system resources in short time and become unresponsive. It also increases the risk of sucessfull attack on the computer)
Expected results:
Firefox should open:
- in a minimal and sandboxed enviroment
- without any default connections
- with maximal privacy and security options turned on
- with only one (main) process and minimal needed usage of system resources
Additionally, it should be compiled with build-in:
-
resource watchdog and leak prevention to prevent that the resource usage get too big
-
optimization for speed
Comment 1•5 years ago
|
||
This is too vague a report to be actionable - it's missing concrete information, and at the same time tries to cover 5 different things.
(In reply to Mcgiwer from comment #0)
- it has a too big working set and system resources usage
It's fine for me. If you see really bizarre working set usage (1TB?), file a specific bug about that with (a lot) more detail. What's the memory used for? How many tabs are open? Do you see this in a clean Firefox profile? Etc.
- firefox opens too many unnessecary and unknown internet connections by default
Again, it's unclear what "too many" means (1? 20? 100?) and why you think they are "unnecessary" (we shouldn't look for updates? Or update our safebrowsing, certificate, add-on and other blocklists that keep you safe? Or be able to do A/B testing? Or check for updates for your add-ons? Or...? Note that you can turn all of these things off if you want, https://support.mozilla.org/en-US/kb/how-stop-firefox-making-automatic-connections ). It's also not clear what you mean by "unknown" in this context.
- it opens too many sub-processess (it should open one main and a one new sub-process for each open tab/window).
No, it shouldn't, it should open however many processes allow it to best function. In this case, we've put e.g. graphics things into its own process, and some network operations get their own process, etc. - all of this helps security and stability, because crashes in those subprocesses ideally don't break the browser, and security compromises are limited to those processes.
Instead of that, it opens many unknown processess
Again, not clear what is "unknown".
and there is not listed in the task manager, with one is to with
You can use about:processes inside Firefox to find out.
Above can create security and DoS risks (system may get out of system resources in short time and become unresponsive. It also increases the risk of sucessfull attack on the computer)
No, it really doesn't.
(In reply to :Gijs (he/him) from comment #1)
It's fine for me. If you see really bizarre working set usage (1TB?), file a specific bug about that with (a lot) more detail. What's the memory used for? How many tabs are open? Do you see this in a clean Firefox profile? Etc.
if you call that that normal then why does the virtual size reach 2 TB and working set (average) 2 GB ?
Again, it's unclear what "too many" means (1? 20? 100?)
With one tab open (to bugzilla), there are 15 connections established
and why you think they are "unnecessary"
they"eating" the network brandwitch
(we shouldn't look for updates? Or update our safebrowsing, certificate, add-on and other blocklists that keep you safe? Or be able to do A/B testing? Or check for updates for your add-ons?
(we shouldn't look for updates? Or update our safebrowsing, certificate, add-on and other blocklists that keep you safe? Or be able to do A/B testing? Or check for updates for your add-ons?
Most of them are ok, but the checks shouldn't be done too often (minimum once per few days or a week, dependenty how often the updates are released). However, there are some connections (most of them are described in the article: https://support.mozilla.org/en-US/kb/how-stop-firefox-making-automatic-connections) with should be turned off as default, including the to the ones to CDN center's (like for example: amazonaws, google user content, etc.). Besides, I don't real know what you mean by A/B testing.
No, it shouldn't, it should open however many processes allow it to best function. In this case, we've put e.g. graphics things into its own process, and some network operations get their own process, etc. - all of this helps security and stability, because crashes in those subprocesses ideally don't break the browser, and security compromises are limited to those processes.
actually firefox isn't already too stable (it can even cause a computer lag or make it inresponsive because of the system resource usage). in my opinion, Firefox should return a bit to the root of being as much lighweight browser as possible with possibility to extend it's functionality. Actually, thru the time it has became a huge, to big system resource demanding monster browser
Again, not clear what is "unknown".
it means that from the process manager is hard to tell with sub-process belongs to with function/tab. It would be nice if for example Firefox (by creating a sub-process) would put next to it's name in round or square brackets name of the function or tab/window for easier identification (foe example if a tab stop to response, it would be easier to kill it process without need to restart the whole browser (thereof I had also suggested to put each tab/window into separate sub-process)
No, it really doesn't.
as far as I know, in both: DoS attack and over usage of system resources by an process the result is the same: system run's out of the system resources and stop to respond to user's input (so called "freeze")
Comment 3•5 years ago
|
||
(In reply to Mcgiwer from comment #2)
(In reply to :Gijs (he/him) from comment #1)
It's fine for me. If you see really bizarre working set usage (1TB?), file a specific bug about that with (a lot) more detail. What's the memory used for? How many tabs are open? Do you see this in a clean Firefox profile? Etc.
if you call that that normal then why does the virtual size reach 2 TB and working set (average) 2 GB ?
I didn't call 1TB normal, I said that would be bizarre. I don't know what specifically you're referring to by 'virtual size' and where the 2TB (!?) measurement comes from, but filing a new bug with more specifics on that particular problem would be useful. 2 terabyte memory usage would definitely not be normal. 2GB might be, depending on what the browser is doing (e.g. my own instance currently uses several gb - but I have 90 tabs open across 6 windows, and a lot of them are memory-hungry web applications) again, more specifics would be useful. You can use about:memory to create a dump that shows us where the memory use is going, for instance, and that might help figure out why you're seeing unusually high memory usage.
the checks shouldn't be done too often (minimum once per few days or a week, dependenty how often the updates are released).
When there are critical security updates, we want people's computers to get those updates as soon as possible. App updates like that are checked once a day; other update checks may happen more frequently to ensure we can respond more quickly if there are critical issues.
However, there are some connections (most of them are described in the article: https://support.mozilla.org/en-US/kb/how-stop-firefox-making-automatic-connections) with should be turned off as default, including the to the ones to CDN center's (like for example: amazonaws, google user content, etc.).
I don't know which specific connections you mean here - from a very casual look at wireshark, I don't see connections to amazonaws or google user content when I start a blank new Firefox instance (though I guess some of our CDN stuff might live there, I'd expect we'd use different domains for the request). Please be specific about which things you mean (and how/where you see the connection being made - are you looking up IP addresses back to DNS names yourself or something?). Is it possible that these connections in fact relate to an open tab and the content the website asks for?
Besides, I don't real know what you mean by A/B testing.
Testing new features or bugfixes by turning them on/off without requiring full Firefox updates (which would use a lot more bandwidth and offer less granular control). It helps us make sure changes don't cause stability or functional problems without having to release them to hundreds of millions of people at once (and then saddling everyone with those problems).
in my opinion, Firefox should return a bit to the root of being as much lighweight browser as possible with possibility to extend it's functionality. Actually, thru the time it has became a huge, to big system resource demanding monster browser
People expect the browser to do much more now than 10 or 20 years ago - run text editing applications, games, play videos, run streaming video conferencing with multiple other participants, etc. It's not possible to do all that without being bigger. At the same time, computers have more memory and disk space than before. If we're using too much memory on specific tasks, please file bugs on that. But generic complaints that Firefox is a "monster browser" aren't actionable and cannot just be "fixed".
Again, not clear what is "unknown".
it means that from the process manager is hard to tell with sub-process belongs to with function/tab. It would be nice if for example Firefox (by creating a sub-process) would put next to it's name in round or square brackets name of the function or tab/window for easier identification
Doing this in the process manager is tricky, because each process can run multiple tabs, and which tabs they run can change, so we'd have to continuously update this - I'm not even sure this is technically feasible.
However, we implemented something similar in Firefox itself already - from Firefox 85 (currently in beta, https://beta.mozilla.org/ ; due for release in January 2021 ) you can get the OS process ID of a given tab from its tooltip (ie by hovering over the tab), if you toggle browser.tabs.tooltipsShowPid to true in about:config . Alternatively, you could use about:processes to get this information (already in release), but that's admittedly more work.
(foe example if a tab stop to response, it would be easier to kill it process without need to restart the whole browser (thereof I had also suggested to put each tab/window into separate sub-process)
Tabs will generally be split over a number of sub-processes right now; process-per-site (not the same as per-tab/window) is currently being worked on, and you can try it out on https://nightly.mozilla.org/ by turning on "Fission" in the experimental section of the Firefox Options/Preferences. Because of how the web works, we cannot do true "process per-tab" if you have multiple tabs open that reference the same site, as websites depend on being able to communicate synchronously with those other tabs, which cannot be done performantly if they're in separate processes.
Description
•