Closed Bug 952693 Opened 6 years ago Closed 6 years ago
The Nuwa process should never be OOM killed
We should never OOM kill the Nuwa process while any app processes are alive, because then there will be app processes spawned from multiple Nuwa template processes, defeating some of the optimization. Since the Nuwa process should be low overhead, I think we should consider even killing the parent process first.
Hi, Kyle, When I try nuwa on device with 128MB memory, I used to adjust nuwa process's priority to the same as parent process in order to prevent it'd been killed by LMK. But I am not sure if this method is a good solution.
Attachment #8350975 - Flags: feedback?(khuey)
6 years ago
Attachment #8350975 - Flags: feedback?(khuey) → feedback+
Bug 957509 would reduce the size of USS of Nuwa to 1.xMB and preallocated process to 0.8MB. The overhead of Nuwa was dramatically drop.
(In reply to Thinker Li [:sinker] from comment #2) > Bug 957509 would reduce the size of USS of Nuwa to 1.xMB and preallocated > process to 0.8MB. The overhead of Nuwa was dramatically drop. Sounds good! Then, are we going to land Kai-Zhen's patch as well? The patch looks like a good solution.
He have applied the patch from cervantes for daily build.
Great. Can Kai-Zhen be the assignee for this bug to make sure this bug already has owner and progress? Thank you.
I think we can get the attached patch reviewed and landed. But it depends on bug 950266. Before bug 950266 got fix nuwa is not enabled in b2g by default.
Thanks. I think it's a good approach. Can you mark review? to ask for review? Thanks.
6 years ago
Attachment #8350975 - Flags: review?(khuey) → review+
Assignee: nobody → kli
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
You need to log in before you can comment on or make changes to this bug.