Open
Bug 883720
Opened 11 years ago
Updated 2 years ago
e10s xpcshell tests leak ContentParent
Categories
(Core :: DOM: Content Processes, defect, P5)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: jduell.mcbugs, Unassigned)
References
(Blocks 2 open bugs)
Details
bent, is this anything to be worried about? When I run e10s xpcshell tests in /netwerk/test/unit_ipc, bloatview reports that they're leaking memory: == BloatView: ALL (cumulative) LEAK STATISTICS, default process 30311 Per-Inst Leaked Total Rem 0 TOTAL 32 2856 9739 3 AsyncChannel 72 72 1 1 8 CondVar 32 32 15 1 9 ContentParent 944 944 1 1 43 Mutex 24 24 108 1 46 PContentParent 768 768 1 1 61 RPCChannel 520 520 1 1 63 RefCountedMonitor 64 64 1 1 70 SyncChannel 176 176 1 1 135 nsFrameMessageManager 112 112 3 1 219 nsTArray_base 8 144 809 18 Most likely suspect seems to be ContentParent. I did a quick, partial regression search--this is not happening on the beta branch as of today (so Firefox 22), but is happening on aurora/nightly.
We should fix it, but since it's just test leaks I wouldn't panic :)
Updated•10 years ago
|
tracking-e10s:
--- → +
Updated•10 years ago
|
Blocks: e10s-tests
Updated•10 years ago
|
Component: IPC → DOM: Content Processes
Updated•6 years ago
|
Blocks: xpcshell-leaks
Updated•6 years ago
|
Priority: -- → P5
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•