Stop using the form factor for detecting memory constrained devices

Bug #1510603 reported by Chris Coulson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Fix Released
Medium
Chris Coulson

Bug Description

We currently use the form factor for detecting memory constrained devices, but this is wrong. A better metric would be the amount of physical memory and swap space available.

Changed in oxide:
importance: Undecided → Low
status: New → Triaged
Changed in oxide:
importance: Low → Medium
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

This is currently used in:

- ContentClient::ShouldOptimizeForMemoryUsage (an Oxide modification to Chromium for limiting decoded image sizes and the discardable shared memory size).
- ContentMainDelegate::PreSandboxStartup for limiting the size of the Skia font cache.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

It's also used in RendererFrameEvictor, but I'd like to refactor how this code works.

Changed in oxide:
status: Triaged → In Progress
assignee: nobody → Chris Coulson (chrisccoulson)
milestone: none → branch-1.15
Revision history for this message
Chris Coulson (chrisccoulson) wrote :
Changed in oxide:
milestone: branch-1.15 → branch-1.16
Changed in oxide:
milestone: branch-1.16 → branch-1.17
Revision history for this message
Chris Coulson (chrisccoulson) wrote :
Revision history for this message
Chris Coulson (chrisccoulson) wrote :
Changed in oxide:
status: In Progress → Fix Committed
Changed in oxide:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.