Closed Bug 1251127 Opened 4 years ago Closed 4 years ago

Gracefully handle multiple calls to nsMemoryReporterManager::Init()

Categories

(Core :: XPCOM, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
mozilla47
Tracking Status
firefox47 --- fixed

People

(Reporter: njn, Assigned: njn)

References

Details

Attachments

(1 file)

In bug 1248587 we have evidence of nsMemoryReporterManager::Init() being called multiple times, which leads to bogus duplication of some memory reports like "resident", "vsize".

It's not clear why, but to avoid problems, we can turn any calls after the first one into a no-op.
Assignee: nobody → n.nethercote
Status: NEW → ASSIGNED
Attachment #8723385 - Flags: review?(erahm) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/c836363a0200fdee85895633cf9725ec5da53c28
Bug 1251127 - Gracefully handle multiple calls to nsMemoryReporterManager::Init(). r=erahm.
https://hg.mozilla.org/mozilla-central/rev/c836363a0200
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla47
You need to log in before you can comment on or make changes to this bug.