I was doing some testing in the past few days on a Flame using the 319MiB memory switch and found that our core apps are now almost unusable on it. Opening a single app seems to end up killing the homescreen and keeping two open at the same time is almost impossible.
So I've got two questions: the first one is, did we significantly regress memory consumption again? Or is it just gecko having grown significantly in the past few weeks making our minimum process size larger? The second question is obviously: do we still care about 256MiB devices? Because if we still do then it looks like we're not in a good spot for a 2.5 release running on those. If we don't care I suppose it's fine though we should still keep our memory consumption under control. If we move our minimum to 512MiB we'll have plenty of room and this might cause us to regress even further almost without noticing (*). I'm running an engineering build BTW, but I don't think this should make much of a difference. Gabriele *) Unless the screen has a rather high resolution, in which case 512MiB might still yield only a small amount of usable memory for apps as most of it will go to the framebuffer and accompanying structures (layers & co).
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
