webbrowser-app

open tabs using too much memory

Bug #1376418 reported by Bill Filler
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
webbrowser-app
Fix Released
Critical
Olivier Tilloy
webbrowser-app (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

See initial report on barajas project:
https://bugs.launchpad.net/barajas/+bug/1376165

Basically we should free the resources of open tabs when they move to the background during the running of the browser as each tab uses much memory and cause the system with low memory, especially on krillin, to start killing everything with the oom killer.

See the details in the barajas report.

Related branches

lp:~osomon/webbrowser-app/unload-webviews
PS Jenkins bot: Approve (continuous-integration)
Diff: 70 lines (+22/-2)
3 files modified
src/app/webbrowser/Browser.qml (+14/-0)
src/app/webbrowser/Chrome.qml (+5/-1)
tests/autopilot/webbrowser_app/tests/__init__.py (+3/-1)
lp:ubuntu/utopic/webbrowser-app
Bill Filler (bfiller)
Changed in webbrowser-app:
importance: Undecided → Critical
assignee: nobody → Olivier Tilloy (osomon)
tags: added: rtm14
Bill Filler (bfiller)
tags: added: touch-2014-10-09
Revision history for this message
Bill Filler (bfiller) wrote :

We should keep at most the last two tabs in memory and free all the rest. Even if this means losing the screenshots of the open tabs, it's better than blowing out memory. When a new tab is requested, the old tabs should freed and we just save the url and display like we do when starting the browser up and not instantiating all the tabs.

Revision history for this message
Bill Filler (bfiller) wrote :

in addition to freeing up tabs when they go to the background, maybe we should change the default behavior when invoking the browser externally to not open in new tabs but open in the current tab. This has the advantage of low overhead and maintains the navigation history in the tab. When we start killing off tabs we loose the navigation history for that tab as well..

Revision history for this message
Olivier Tilloy (osomon) wrote :

> we loose the navigation history for that tab as well..

That will be addressed when bug #1353143 is fixed.

Olivier Tilloy (osomon)
Changed in webbrowser-app:
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package webbrowser-app - 0.23+14.10.20141003-0ubuntu1

---------------
webbrowser-app (0.23+14.10.20141003-0ubuntu1) utopic; urgency=low

  [ CI bot ]
  * Resync trunk

  [ Alexandre Abreu ]
  * Add a simple mechanism (simpler than the one already in place) to
    override user agents for a given webapp. (LP: #1370975)

  [ Alberto Mardegan ]
  * Fix handling of host cookies

  [ Olivier Tilloy ]
  * Ship a PNG icon instead of an SVG, and install it under the app’s
    own data dir. (LP: #1365408)
  * Make an autopilot test more robust by ensuring that the drawer menu
    is dismissed but not clicked. (LP: #1365304)
  * Persistently cache favicons on disk to avoid re-downloading them
    across application runs. (LP: #1340585)
  * Ensure that at most 2 webviews are instantiated at all times, to
    reduce memory consumption. (LP: #1376418)
 -- Ubuntu daily release <email address hidden> Fri, 03 Oct 2014 14:42:27 +0000

Changed in webbrowser-app (Ubuntu):
status: New → Fix Released
Olivier Tilloy (osomon)
Changed in webbrowser-app:
status: In Progress → Fix Released
Bill Filler (bfiller)
Changed in webbrowser-app (Ubuntu):
importance: Undecided → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.