Bug 1767346 Comment 18 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
This actually broke priorityHint even further, so I'm gonna ask the sheriff to revert.

To reproduce in Fenix:

*  Open Fenix and load a web page, verify that /proc/<pid>/oom_score is below 100 for the tab:XX process (can check the PID with ps -A | grep org.mozilla)
* Background Fenix -> oom_score should still be below 100, in my testing it's around 770

reverting the patch fixes this.

I'll separately land a test that will cover this case.
Revision 1 by
on 
This actually broke priorityHint even further, so I'm gonna ask the sheriffs to revert.

To reproduce in Fenix:

*  Open Fenix and load a web page, verify that /proc/<pid>/oom_score is below 100 for the tab:XX process (can check the PID with ps -A | grep org.mozilla)
* Background Fenix -> oom_score should still be below 100, in my testing it's around 770

reverting the patch fixes this.

I'll separately land a test that will cover this case.
Revision 2 by
on 
This actually broke priorityHint even further, so I'm gonna ask the sheriffs to revert.

To reproduce in Fenix:

*  Open Fenix and load a web page, verify that `/proc/<pid>/oom_score` is below 100 for the `tab:XX` process (can check the PID with `ps -A | grep org.mozilla`)
* Background Fenix -> `oom_score` should still be below 100, in my testing it's around 770

reverting the patch fixes this.

I'll separately land a test that will cover this case.

Back to Bug 1767346 Comment 18