I’ve changed the threshold to 100MB and tested on my M10. This is too low, the system OOM killer kicks in before the browser gets a chance to unload background tabs:
May 2 16:25:39 ubuntu-phablet kernel: [ 3173.400686] (0)[54:kswapd0]lowmemorykiller: Killing 'webbrowser-app' (7341), adj 1, score_adj 110, May 2 16:25:39 ubuntu-phablet kernel: [ 3173.400686] to free 550600kB on behalf of 'kswapd0' (54) because May 2 16:25:39 ubuntu-phablet kernel: [ 3173.400686] cache 65196kB is below limit 65536kB for oom_score_adj 12 May 2 16:25:39 ubuntu-phablet kernel: [ 3173.400686] Free memory is 4344kB above reserved Note that in my tests I had several apps open (both native and webapps, 4 of them in total) plus the browser with a dozen tabs including a live hangout, a google doc being edited, google maps, google plus, facebook and a 1080p movie trailer playing in youtube. The last "free memory" value reported by the browser before it was killed was 237980KB, i.e. 232MB. Note that this value is not just the free RAM, it’s the sum of the following entries from /proc/meminfo: MemFree Buffers Cached (https://bazaar.launchpad.net/~phablet-team/webbrowser- app/trunk/view/head:/src/app/meminfo.cpp#L83) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1576639 Title: memory threshold is too high Status in Canonical Device Images: New Status in Canonical System Image: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When opening new tabs in the browser, it decides if it should close existing ones based on level of free memory available in the system. My understanding is that this is currenly set to 30% percentage of memory in the device. There are two issues with this approach and setting: 1) a percentage means that the threshold changes from device to device. While theamount of memory needed to open a webpage is not device specific. For example at 30%, the browser would close open tabs if there less than 1.2Gb mem free in a 4Gb device, but will only need 300Mb free on a 1Gb device. This is a very large difference. 2) In M10 with 2Gb it requires 600mb free. From idle, just opening the gmail in the browser, takes the avilable system memory below this. This means that in 2gb devices the threshold is never met, and the browser never runs more than one tab at the same time. this impacts user experience, specially in desktop mode. For example is not possible to open a document in the browser while attending a hangout. How to reproduce open a tab in the browser, go to youtube and play any video then open a new tab expected: music/sound in the video continues to play actual in m10: sound stops playing shortly after opening the tab To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-device-images/+bug/1576639/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
