Check Content Viewer cache size in nsSHistory for fission
Categories
(Core :: DOM: Navigation, defect, P3)
Tracking
()
| Fission Milestone | Future |
People
(Reporter: jesup, Unassigned)
Details
(Whiteboard: [fission][memshrink])
We may want to adjust the content viewer cache sizes for fission; they may be wildly too large in a fission world. See https://searchfox.org/mozilla-central/source/docshell/shistory/nsSHistory.cpp#291
These numbers for desktop were set in 2005....
|
Reporter | |
Updated•3 years ago
|
|
||
Comment 1•3 years ago
|
||
Currently bfcache isn't enabled for Fission. But the value might in theory be too large for e10s too.
Though, of course computers have a lot more memory these days, though also web sites are way more complicated.
|
|
||
Updated•3 years ago
|
|
||
Updated•3 years ago
|
|
||
Comment 3•3 years ago
|
||
Tracking for Fission MVP. We want to enable Fission bfcache before shipping to Beta, but it doesn't necessarily block our Beta experiment (M7).
|
|
||
Comment 4•3 years ago
|
||
This is not really a Fission issue. Pretty much the same applies to e10s.
|
|
||
Comment 5•1 year ago
|
||
Or not really a ship issue either. In fact with Fission we should store again the same amount of contentcontentviewers than before e10s and those numbers look quite reasonable.
We can tweak the limits if we see some issues or if there are cases where user experience could be improved.
Description
•