Closed Bug 1670433 Opened 4 years ago Closed 2 years ago

Check Content Viewer cache size in nsSHistory for fission

Categories

(Core :: DOM: Navigation, defect, P3)

Product:
Core
Component:
DOM: Navigation
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Project Flags:
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....

Flags: needinfo?(continuation)

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.

Yes, what Olli said.

Flags: needinfo?(continuation)
Severity: -- → S3
Priority: -- → P3

Tracking for Fission MVP. We want to enable Fission bfcache before shipping to Beta, but it doesn't necessarily block our Beta experiment (M7).

Fission Milestone: --- → MVP

This is not really a Fission issue. Pretty much the same applies to e10s.

Fission Milestone: MVP → Future

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.

No longer blocks: fission-bfcache
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.