[regression] OOM killer too aggressive since update 10? [duplicate]

asked 2014-12-28 21:44:58 +0200

Mario gravatar image

updated 2014-12-29 09:39:06 +0200

eric gravatar image

According to the release notes the Jolla update 10 (1.1.1.27) has a new "out of memory killer". Though, since this update it is nearly impossible to use the Firefox Android app.

If Firefox is the only app running, it does not crash (immediately). With other apps in the background it either crashes immediately or just after opening a website. That's why I assume it's killed by the OOM killer.

However, before update 10 I could use firefox just fine. So, maybe the OOM killer has become too aggressive with this update?

Best regards, Mario

[Update] After some additional testing I'm not so sure about the reproducability of my bug report. While the problem still persisted after closing all apps and still after restarting Alien Dalvik over the new Utility app, I cannot reproduce the issue after rebooting my Jolla.

Dear community, please report if and when you have similar problems.

edit retag flag offensive reopen delete

The question has been closed for the following reason "duplicate question" by Alex
close date 2014-12-28 23:44:27.456085

Comments

Dear Mario, this is a duplicate of https://together.jolla.com/question/72016/browser-and-oom-handling-with-update-10/ and there is an ongoing discussion regarding this issue. You also will find some workarounds which you are able to achieve with tweaking using terminal. :)

Alex ( 2014-12-28 23:44:18 +0200 )edit

Cool, thank you. Sorry for double posting.

Mario ( 2014-12-29 00:00:32 +0200 )edit

Just a quick observation: this post may be a duplicate but has a better title than the first one.

pichlo ( 2014-12-29 11:11:59 +0200 )edit

we need a merging feature!

jolladiho ( 2014-12-29 11:20:42 +0200 )edit