Closed Bug 974540 Opened 12 years ago Closed 12 years ago

nsMemoryReporterManager's count of child processes is wrong when Nuwa is enabled

Categories

(Toolkit :: about:memory, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla30

People

(Reporter: jld, Assigned: jld)

References

Details

(Whiteboard: [MemShrink])

Attachments

(1 file, 1 obsolete file)

If Nuwa is enabled, the nsMemoryReporterManager's count of child processes will include Nuwa but not Nuwa's children, which is exactly the opposite of what's supposed to happen. This means that the count is (usually?) always 1, which causes only the first child to respond to be included in the report.
Whiteboard: [MemShrink]
Comment on attachment 8378450 [details] [diff] [review] bug974540-memchild-nuwa-count-hg0.diff Review of attachment 8378450 [details] [diff] [review]: ----------------------------------------------------------------- If the Nuwa process is ever killed and reborn the number here will get out of sync.
Attachment #8378450 - Flags: review?(khuey) → review-
The fix is simple. Tested by manually SIGKILL'ing Nuwa a few times.
Attachment #8378450 - Attachment is obsolete: true
Attachment #8383389 - Flags: review?(khuey)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: