On 01/22/2016 08:30 AM, Naoki Hirata wrote:
> As far as I know gecko doesn't handle long lists of scrolling through
> large images very well.
> It could very well explain the OOMing.
That's not true. Gecko should actually be quite good at that, decoding
on demand etc. But it's very possible that the add-on is doing something
that trips our heuristics.
> It would still cause me some concerns that we didn't kill that app
> before it killed the b2g process.
> Would it be possible for us to sign up for the Twitter addon? I think
> we would still want to investigate why we didn't LMK the app before it
> caused system issues.
That's because the memory usage in the app is low (~ 15MB). All the
badness happens in the parent process. The issue is not in the OOM
killer itself.
Fabrice
--
Fabrice Desré
b2g team
Mozilla Corporation
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos
