Lower the limit for base::DiscardableMemoryAllocator in the browser
Bug #1498953 reported by
Chris Coulson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical System Image |
Fix Released
|
High
|
Pat McGowan | ||
| Oxide |
Fix Released
|
High
|
Chris Coulson | ||
| 1.10 |
Fix Released
|
High
|
Chris Coulson | ||
| 1.9 |
Fix Released
|
High
|
Unassigned | ||
Bug Description
Chrome on Android sets a limit of 128MB, whereas it's currently set to 512MB for us. DiscardableMemory is allocated by the browser process on behalf of renderers, and is used extensively in Blink for decoded image data
| Changed in oxide: | |
| assignee: | nobody → Chris Coulson (chrisccoulson) |
| milestone: | none → branch-1.11 |
| importance: | Undecided → High |
| status: | New → Fix Released |
Revision history for this message
| David Barth (dbarth) wrote | #1 |
| Changed in canonical-devices-system-image: | |
| assignee: | nobody → Pat McGowan (pat-mcgowan) |
| importance: | Undecided → High |
| milestone: | none → ww40-2015 |
| status: | New → Confirmed |
| Changed in canonical-devices-system-image: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Jean-Baptiste Lallement (jibel) wrote | #2 |
| Changed in canonical-devices-system-image: | |
| status: | In Progress → Fix Committed |
| Changed in canonical-devices-system-image: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
@Chris: can this change be backported to the stable line?
At least the part that doesn't add the extra form-factor functions, but changes the memory limits. The form factor determination could still be approximated by architecture == armhf in the foreseeable 6 weeks of lifetime for this stable release.