To be clear, the chromium content api is using a common technique of opening a file to get a handle then deleting the file. It hasn't closed the files yet because it still needs to use the shared memory. If the OOM killer is firing too often on oxide on constrained devices (like these phones), then it should be adjusted to not do that (android is able to use chrome (which uses the same code) without killing it off-- we should do the same).
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1497924 Title: oxide-renderer heavily uses /run/shm To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1497924/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
