Comment 10 for bug 1478853

Revision history for this message
Ted Gould (ted) wrote : Re: [Bug 1478853] Re: OOM scoring kills the browser's render process while the browser is running

On Tue, 2015-08-04 at 20:43 +0000, Gerry Boland wrote:

> You're correct the OOM score set to 2 arbitrary values. They're
> hardcoded and set by upstart-app-launch. I believe your question is my
> question 2 above, to which I don't have an answer.

They're not entirely arbitrary, more or less built to try and have a
continuum of values. Basically trusted services (unity, etc.) are zero.
Then we put the focused application below that at 100. The dash is 200
so if there is no focused application it is the lowest. Then unfocused
applications are 900.

Hand-wavingly that means that a focused application would be allowed to
use 8 times as much memory as an unfocused application if memory size
was the only thing taken into account.