** Description changed: 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 + + + [Manual test case for verification] + On various devices (desktop with large amount of physical memory, tablet, phone, …), open the browser, open a number of tabs and browse to pages known to require a large amount of memory (Gmail, G+, hangouts, youtube, Google maps, webgl games, …). + Monitor the amount of available memory (e.g. using top) and verify that when the device is getting low on memory some cleanup is performed (background tabs are being unloaded) such that the OOM killer nevers kicks in, taking down the entire application. + Verify that the mechanism is not too aggressive, i.e. that not all background tabs get unloaded all the time (having a background tab playing some audio is a good idea to easily spot when it’s being unloaded). + As this mechanism is based on heuristics, it will never be 100% perfect, but the situation should have greatly improved.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576639 Title: memory threshold is too high To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-device-images/+bug/1576639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
