https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263436
--- Comment #4 from Josef 'Jeff' Sipek <jef...@josefsipek.net> ---
Sorry for the delay. I about mid-way through my multi-day data "collection", I
upgraded to firefox 100 and so I wanted to give it enough time to see what it
behaves like. Observations:
* Firefox 100 seems a little better than 99
* The memory usage growth seems to be a function of how many (not which)
websites I visit. "Vigorous" browsing will run up the process size much faster
than more casual browsing.
* Having approximately 20 firefox ~150-380MB processes mostly idle along with
the 1.4GB main process chews up about 1/3 of the system RAM.
* The main process is the major memory hog - the other processes, while not
lightweight, tend to be more reasonable.
* The about:memory output doesn't show anything that jumps out at me (aside
from the ridiculous vsize/resident and max vsize/resident values).
Is there a way to tell firefox that even though the machine has 16GB, I'd like
to keep some memory for the ARC, kernel, and other processes?
Main process's about:memory headings & summary:
563.47 MB (100.0%) -- explicit
├──364.26 MB (64.65%) -- gfx
16.18 MB (100.0%) -- decommitted
6,172 (100.0%) -- event-counts
16 (100.0%) -- extensions
379.84 MB (100.0%) -- gfx
4.35 MB (100.0%) -- images
249 (100.0%) -- ipc-channels
285 (100.0%) -- ipc-channels-peak
502 (100.0%) -- js-component-loader
4 (100.0%) -- js-helper-threads
90.11 MB (100.0%) -- js-main-runtime
33.00 MB (100.0%) -- js-main-runtime-gc-heap-committed
22 (100.0%) -- js-main-runtime-realms
58 (100.0%) -- message-manager
1,973 (100.0%) -- observer-service
747 (100.0%) -- observer-service-suspect
674 (100.0%) -- preference-service
0 (100.0%) -- queued-ipc-messages
0.14 MB (100.0%) -- shared-string-bundles
7.77 MB (100.0%) -- window-objects
1.50 MB ── font-list-shmem
2.18 MB ── gfx-surface-image
0.00 MB ── gfx-textures
0.00 MB ── gfx-textures-peak
0.00 MB ── gfx-tiles-waste
0 ── ghost-windows
3 ── imagelib-surface-cache-already-present-count
0.58 MB ── imagelib-surface-cache-estimated-locked
0.64 MB ── imagelib-surface-cache-estimated-total
146 ── imagelib-surface-cache-image-count
174 ── imagelib-surface-cache-image-surface-count
94 ── imagelib-surface-cache-locked-image-count
115 ── imagelib-surface-cache-locked-surfaces-count
0 ── imagelib-surface-cache-overflow-count
0 ── imagelib-surface-cache-table-failure-count
59 ── imagelib-surface-cache-tracked-cost-count
59 ── imagelib-surface-cache-tracked-expiry-count
0 ── imagelib-surface-cache-tracking-failure-count
2.06 MB ── js-main-runtime-temporary-peak
4,992 ── page-faults-hard
13,369,887 ── page-faults-soft
1,710.35 MB ── private
1,362.16 MB ── resident
1,448.52 MB ── resident-peak
2.04 MB ── shmem-allocated
126.62 MB ── shmem-mapped
0 ── unresolved-ipc-responses
20,886.48 MB ── vsize
8,191.63 MB ── vsize-max-contiguous
0.00 MB ── wasm-runtime
--
You are receiving this mail because:
You are the assignee for the bug.
