The default bug view has changed. See this FAQ.

[B2G] Lower image.mem.max_decoded_image_kb

RESOLVED FIXED

Status

Firefox OS
General
RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: Justin Lebar (not reading bugmail), Assigned: Justin Lebar (not reading bugmail))

Tracking

(Blocks: 1 bug)

unspecified
ARM
Linux

Firefox Tracking Flags

(blocking-basecamp:+, firefox18 fixed)

Details

(Whiteboard: [MemShrink])

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
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

5 years ago
Created attachment 672476 [details] [diff] [review]
Patch, v1
Attachment #672476 - Flags: review?(joe)
(Assignee)

Comment 2

5 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

5 years ago
Assignee: nobody → justin.lebar+bug
Attachment #672476 - Flags: review?(joe) → review+
(Assignee)

Comment 3

5 years ago
Thanks, Joe.

https://hg.mozilla.org/integration/mozilla-inbound/rev/bd5e49f6d2fa
(Assignee)

Updated

5 years ago
status-firefox18: --- → affected
(Assignee)

Updated

5 years ago
Whiteboard: [MemShrink]
https://hg.mozilla.org/mozilla-central/rev/bd5e49f6d2fa
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
blocking-basecamp: ? → +
(Assignee)

Comment 5

5 years ago
https://hg.mozilla.org/releases/mozilla-aurora/rev/84573f69513c
status-firefox18: affected → fixed
(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

5 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.