Closed
Bug 802777
Opened 12 years ago
Closed 12 years ago
[B2G] Lower image.mem.max_decoded_image_kb
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(blocking-basecamp:+, firefox18 fixed)
People
(Reporter: justin.lebar+bug, Assigned: justin.lebar+bug)
References
Details
(Whiteboard: [MemShrink])
Attachments
(1 file)
1.20 KB,
patch
|
joe
:
review+
|
Details | Diff | Splinter Review |
image.mem.max_decoded_image_kb tracks the amount of decoded image data we "willingly" keep around. Even if you set this value to 0, we often unwillingly keep around a lot more than this. For example, all images on a page are always decoded (bug 689623). But if we're using more than image.mem.max_decoded_image_kb memory for decoded image data and we are able to throw any of our decoded data, we'll do so.
Assignee | ||
Comment 1•12 years ago
|
||
Attachment #672476 -
Flags: review?(joe)
Assignee | ||
Comment 2•12 years ago
|
||
I can't ask for approval-aurora on patches in the b2g component, so I guess I have to ask for blocking.
blocking-basecamp: --- → ?
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → justin.lebar+bug
Updated•12 years ago
|
Attachment #672476 -
Flags: review?(joe) → review+
Assignee | ||
Comment 3•12 years ago
|
||
Thanks, Joe. https://hg.mozilla.org/integration/mozilla-inbound/rev/bd5e49f6d2fa
Assignee | ||
Updated•12 years ago
|
status-firefox18:
--- → affected
Assignee | ||
Updated•12 years ago
|
Whiteboard: [MemShrink]
Comment 4•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/bd5e49f6d2fa
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
blocking-basecamp: ? → +
Assignee | ||
Comment 5•12 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/84573f69513c
Comment 6•12 years ago
|
||
(In reply to Justin Lebar [:jlebar] from comment #0) > Even if you set this value to 0, we often unwillingly keep around a lot more > than this. For example, all images on a page are always decoded (bug > 689623). Doesn't pref("content.image.allow_locking", false); on b2g mean this isn't true for b2g?
Assignee | ||
Comment 7•12 years ago
|
||
(In reply to Timothy Nikkel (:tn) from comment #6) > (In reply to Justin Lebar [:jlebar] from comment #0) > > Even if you set this value to 0, we often unwillingly keep around a lot more > > than this. For example, all images on a page are always decoded (bug > > 689623). > > Doesn't pref("content.image.allow_locking", false); on b2g mean this isn't > true for b2g? Correct.
You need to log in
before you can comment on or make changes to this bug.
Description
•