Stop using the form factor for detecting memory constrained devices
Bug #1510603 reported by
Chris Coulson
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.
Related branches
Changed in oxide: | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in oxide: | |
importance: | Low → Medium |
Changed in oxide: | |
status: | Triaged → In Progress |
assignee: | nobody → Chris Coulson (chrisccoulson) |
milestone: | none → branch-1.15 |
Changed in oxide: | |
milestone: | branch-1.15 → branch-1.16 |
Changed in oxide: | |
milestone: | branch-1.16 → branch-1.17 |
Changed in oxide: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is currently used in:
- ContentClient: :ShouldOptimize ForMemoryUsage (an Oxide modification to Chromium for limiting decoded image sizes and the discardable shared memory size). gate::PreSandbo xStartup for limiting the size of the Skia font cache.
- ContentMainDele