Closed Bug 1003596 Opened 11 years ago Closed 5 years ago

Initialize Gecko preferences according to device memory configuration

Categories

(Firefox for Android Graveyard :: General, defect)

All
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: rnewman, Unassigned)

References

Details

(Whiteboard: [MemShrink:P2])

Follow-on from Bug 792139. Rather than responding only to a low-memory event, we should proactively swizzle image caching etc.
Whiteboard: [MemShrink]
Can we get a list of specific preferences that might be changed?
Whiteboard: [MemShrink] → [MemShrink:P2]
Bug 792139 comment 7, as well as image.mem.max_decoded_image_kb mentioned earlier in that bug.
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.