So when the page becomes blank, that means that the system killed the renderer process because it considered that it was using too much memory. When that happens, could you grep for 'oxide-renderer' in /var/log/syslog, and paste the relevant section (see comment #1 in this report for how it looks like).
Information about the pages you were browsing (if it’s not confidential) would be helpful, as well as whether you were running many apps (particularly webapps that use the oxide renderer process too). Thanks! -- 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/oxide/+bug/1443019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
