I can reproduce on krillin, with the latest vivid-proposed image (#184). Relevant output from /var/log/syslog:
Apr 14 19:01:49 ubuntu-phablet kernel: [ 6435.958540]select 'unity8-dash' (2512), adj 50, size 14703, to kill Apr 14 19:01:49 ubuntu-phablet kernel: [ 6435.958570]select 'webbrowser-app' (9421), adj 110, size 16248, to kill Apr 14 19:01:49 ubuntu-phablet kernel: [ 6435.958590]select 'oxide-renderer' (16584), adj 300, size 150274, to kill Apr 14 19:01:49 ubuntu-phablet kernel: [ 6435.958613]Killing 'oxide-renderer' (16584), adj 300, Apr 14 19:01:49 ubuntu-phablet kernel: [ 6435.958617] to free 601096kB on behalf of 'CompositorTileW' (16593) because Apr 14 19:01:49 ubuntu-phablet kernel: [ 6435.958622] cache 65364kB is below limit 65536kB for oom_score_adj 12 Apr 14 19:01:49 ubuntu-phablet kernel: [ 6435.958627] Free memory is -3272kB above reserved [gfp(0x200da)] So technically, the browser doesn’t crash, but the renderer process is being killed by the system to free up memory. The browser should certainly display a user-friendly message when that happens, instead of just a blank page (tracked by bug #1375272). However I doubt you’ll ever be able to view that page in its entirety on this device, given the memory constraints. ** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed ** Summary changed: - browser crashes on image-heavy pages + renderer process is killed on image-heavy pages on krillin ** Also affects: webbrowser-app Importance: Undecided Status: New ** Changed in: webbrowser-app Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443019 Title: renderer process is killed on image-heavy pages on krillin To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1443019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs