Firefox uses 2.7 GB Memory on startup with blank tab
about:memory details:
Main Process Explicit Allocations 149.91 MB (100.0%) ++ explicit
Other Measurements 30.75 MB (100.0%) ++ decommitted 81.16 MB (100.0%) ++ js-main-runtime 353 (100.0%) ++ js-main-runtime-compartments 49.24 MB (100.0%) ++ js-main-runtime-gc-heap-committed 0 (100.0%) -- low-memory-events ├──0 (100.0%) ── physical └──0 (100.0%) ── virtual
65 (100.0%) ++ message-manager 644 (100.0%) ++ observer-service 383 (100.0%) ++ preference-service 3.30 MB (100.0%) ++ window-objects
6.15 MB ── gfx-d2d-surface-cache
4.01 MB ── gfx-d2d-surface-vram
15.52 MB ── gfx-d2d-vram-draw-target
3.78 MB ── gfx-d2d-vram-source-surface
16.15 MB ── gfx-surface-image
0.00 MB ── gfx-textures
0 ── ghost-windows
30.38 MB ── gpu-committed
0.00 MB ── gpu-dedicated
55.73 MB ── gpu-shared
88.51 MB ── heap-allocated
93.79 MB ── heap-committed
10.65% ── heap-overhead-ratio
0 ── host-object-urls
6.16 MB ── images-content-used-uncompressed
77.00 MB ── js-main-runtime-gc-heap
0.21 MB ── js-main-runtime-temporary-peak
0 ── low-commit-space-events
298.11 MB ── private 289.85 MB ── resident
3.40 MB ── storage-sqlite
651.40 MB ── vsize
Ọ̀nà àbáyọ tí a yàn
Umm, why is the comma in that position:
2,62,604K
There are not enough digits to start counting gigabytes.
If you click in the Performance tab, Resource Monitor button, Memory section, does it show the same oddity?
Ka ìdáhùn ni ìṣètò kíkà 👍 1All Replies (6)
Firefox certainly should not be using that amount of memory on startup with a blank tab something is going badland wrong. You have quite a few addons. As a troubleshooting step let's check Firefox itself is ok.
You did well to have found about:memory. You may even have already tried this.
- Try Firefox in safe mode,and with all plugns disabled. See:
Diagnose Firefox issues using Troubleshoot Mode
Disable or remove Add-ons_how-to-disable-plugins - Then from safe mode but this time with a new additional clean profile.
Profile Manager - Create, remove or switch Firefox profiles_creating-a-profile - Please post back with how you get on. I would expect that Firefox will now open without memory issues.
- Is that correct ?
- What happens after some browsing and restarting is it still ok when used in the above configuration ?
This forum can not take the gzipped about:memory files and it is not easy to paste in anything but short extracts of the text version either. A third party public dropbox type site will need to be used to share the gzipped files. Our pastebin may be used for the textfiles.
- http://pastebin.mozilla.org/
(I would suggest retain the original and post for 1 month).
The gzipped file will be still be needed if anyone wishes to work with the full results.
In fact looking at what you posted are you getting the 2.7GB from a Windows report or something ?
You are showing,
Main Process Explicit Allocations 149.91 MB (100.0%) ++ explicit
that can not be a problem
Here is the first few lines of my current results, much higher than your about:memory results, but much less than your thread title says.
1,107.71 MB (100.0%) -- explicit ├────505.49 MB (45.63%) -- window-objects │ ├──239.00 MB (21.58%) ++ (165 tiny) │ ├──214.26 MB (19.34%) -- top(about:memory, id=723) │ │ ├──213.44 MB (19.27%) -- active/window(about:memory) │ │ │ ├──192.58 MB (17.39%) -- dom │ │ │ │ ├──191.56 MB (17.29%) ── orphan-nodes │ │ │ │ └────1.02 MB (00.09%) ++ (5 tiny) │ │ │ ├───20.07 MB (01.81%) -- js-compartment([System Principal], about:memory) │ │ │ │ ├──19.51 MB (01.76%) -- objects │ │ │ │ │ ├──19.37 MB (01.75%) -- gc-heap │ │ │ │ │ │ ├──12.11 MB (01.09%) ── ordinary │ │ │ │ │ │ └───7.26 MB (00.66%) ++ (2 tiny) │ │ │ │ │ └───0.14 MB (00.01%) ++ (2 tiny) │ │ │ │ └───0.56 MB (00.05%) ++ (6 tiny) │ │ │ └────0.79 MB (00.07%) ++ (2 tiny) │ │ └────0.81 MB (00.07%) ++ cached/window(http://pastebin.mozilla.org/)
Note the line wrapping can not be prevented without further editing but enclose the pasted results within < preformat > tags:
<pre>
block
of pre formatted text
e.g. about:memory text
</pre>
Hi John
Thanks for your reply. The GB have given is from task manager of windows 7. However it matches on checking about:memory in Firefox. In FF, if you add all numbers given in Explicit Allocations and Other Measurements is total which matches in task manager.
Max values that i have noticed are given below when totaled up is around 2600GB!!!
366 (100.0%) ++ js-main-runtime-compartments 399 (100.0%) ++ preference-service 661 (100.0%) ++ observer-service 311.12 MB ── private 303.21 MB ── resident 655.65 MB ── vsize
See Attached Images.
Also see gzipped files at http://pastebin.mozilla.org/3948981
Ọ̀nà àbáyọ Tí a Yàn
Umm, why is the comma in that position:
2,62,604K
There are not enough digits to start counting gigabytes.
If you click in the Performance tab, Resource Monitor button, Memory section, does it show the same oddity?
Actually i think i was reading it in terms of MB where as it is KB (Task Manager).
My oversight. Thanks John and Thanks Jscher for your help.
Thanks for posting back.
I guess you may not have a problem with Firefox.
Something odd seems to be happening with your task manager results. That could have been a temporary glitch. You may find after a restart that the task manager is back to normal.