Open Bug 1834268 Opened 2 years ago Updated 2 months ago

Stop trying to minimize Sqlite memory

Categories

(Core :: SQLite and Embedded Database Bindings, task, P3)

task

Tracking

()

ASSIGNED

People

(Reporter: mak, Assigned: mak)

References

(Blocks 1 open bug)

Details

We use the connections array to minimime sqlite memory when we receive a minimize memory notification.
Because we choose at runtime the maximum amount of memory each connection can use, this has a very limited effect, it's likely in the best case we can save a few MiBs, that are unlikely to make a big difference. If a consumer plans to use a larger cache (e.g. Places has a large cache connection for the urlbar) it could minimize memory itself.

Here is the current proposal:

  1. stop handling the minimize memory topic globally
  2. Have Sqlite.sys.mjs do it for its consumers (vast majority, included the Places large connection)
  3. let cpp consumers handle it by themselves where necessary
Assignee: nobody → mak
Status: NEW → ASSIGNED
Product: Toolkit → Core
You need to log in before you can comment on or make changes to this bug.