Closed Bug 1757725 Opened 3 years ago Closed 3 years ago

Expire page data in memory when no longer needed

Categories

(Toolkit :: Places, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
100 Branch
Tracking Status
firefox100 --- fixed

People

(Reporter: mossop, Assigned: mossop)

Details

Attachments

(1 file)

No description provided.

Currently we cache page data in memory until the browser is closed but this is
too long. We know there could be a couple of consumers of page data, snapshots
and AVM being two so we want to keep any discovered data in memory until we
know that no-one is interested anymore.

This adds a cache and a way for an "actor" (ugh!) to register interest in a url.
As long as there is an actor interested in a url any data for that url will be
cached in memory.

The idea is that when we start tracking a new interaction we start caching any
data for that url. When interactions have been flushed to disk and we've made
any decision about snapshotting we allow the data to expire.

We also by default keep data in the cache until the browser it came from is
destroyed.

Later the AVM can keep a page's data alive until it no longer exists in the
river.

Severity: -- → N/A
Priority: -- → P3
Attachment #9266060 - Attachment description: WIP: Bug 1757725: Expire page data in memory when no longer needed. → Bug 1757725: Expire page data in memory when no longer needed. r=Standard8
Pushed by dtownsend@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6f2e9d9901df Expire page data in memory when no longer needed. r=Standard8
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: