20921 ? Ssl 0:02 webbrowser-app 20966 ? Sl 0:00 /usr/bin/python3 /usr/lib/dbus-property-service/propertyservice 20977 ? S 0:00 /usr/lib/arm-linux-gnueabihf/oxide-qt/chrome-sandbox /usr/lib/arm-linux-gnueabihf/oxide-qt/oxide-renderer --t 20980 ? S 0:00 /usr/lib/arm-linux-gnueabihf/oxide-qt/oxide-renderer --type=zygote --form-factor=phone --limit-max-decoded-im 20985 ? S 0:00 /usr/lib/arm-linux-gnueabihf/oxide-qt/oxide-renderer --type=zygote --form-factor=phone --limit-max-decoded-im 21005 ? Sl 0:00 /usr/lib/arm-linux-gnueabihf/oxide-qt/oxide-renderer --type=renderer --disable-touch-editing --enable-overlay
phablet@arale:~$ l /proc/20980/oom_* /proc/20980/oom_adj /proc/20980/oom_score /proc/20980/oom_score_adj phablet@arale:~$ cat /proc/20985/oom_* 2 111 110 phablet@arale:~$ cat /proc/21005/oom_* 5 313 300 phablet@arale:~$ cat /proc/20921/oom_* 2 142 110 phablet@arale:~$ cat /proc/20977/oom_* 2 110 110 phablet@arale:~$ cat /proc/20980/oom_* 2 114 110 Why has the renderer process such different oom score settings? Intended? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1478853 Title: OOM scoring kills the browser's render process while the browser is running To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
