Closed Bug 1068285 Opened 10 years ago Closed 7 years ago

Investigate why we have multiple default processes in B2G M9

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: mccr8, Unassigned)

Details

As seen in bug 1068280, we seem to have two default processes reporting leaks, maybe into a single log.  I'm not sure if it is okay to have multiple default processes, whether they should somewhere be printing into separate logs (if they aren't already) and so on.  XPCOM may not be the right component either.
Whiteboard: [MemShrink]
Whiteboard: [MemShrink]
Summary: Investigate why we have multiple default processes reporting leaks → Investigate why we have multiple default processes in B2G M9
I filed bug 1068869 for not dumping multiple default processes into a single log, so I'll leave this one open for figuring out why in the world we have multiple default processes.
The only things I see in the log for the extra default process are this:
[714] WARNING: Tried to RegisterCallback without an AtExitManager: file ../../../gecko/ipc/chromium/src/base/at_exit.cc, line 40
That appears 4 times.

That plus the bloat view.  The process leaks 1 Mutex, 1 ReentrantMonitor, 1 XPTInterfaceInfoManager, 1 nsStringBuffer and 1 xptiWorkingSet, which sounds generic.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.