Andrew McCreight [:mccr8] Reporter
	Description • 9 years ago

Similar to bug 1219369, when Nightly was merged over to Aurora some leaks showed up, with my new fine-grained leak detector for the content process:

TEST-UNEXPECTED-FAIL | leakcheck | tab process: leaked too many CondVar (expected 3, got 7)
TEST-UNEXPECTED-FAIL | leakcheck | tab process: leaked too many Mutex (expected 3, got 11)
TEST-UNEXPECTED-FAIL | leakcheck | tab process: leaked too many PImageContainerChild (expected 0, got 4)
TEST-UNEXPECTED-FAIL | leakcheck | tab process: leaked too many PTextureChild (expected 0, got 4)
TEST-UNEXPECTED-FAIL | leakcheck | tab process: leaked too many SharedMemory (expected 0, got 4)
TEST-UNEXPECTED-FAIL | leakcheck | tab process: leaked too many TextureChild (expected 0, got 4)
TEST-UNEXPECTED-FAIL | leakcheck | tab process: leaked too many WeakReference<MessageListener> (expected 2, got 10)

This is a new leak detector that I added recently, so it is possible we also were leaking these objects the last time Nightly was merged to Aurora, but we just didn't notice.

I think this leak is happening in a child process created while running dom/media/tests/mochitest/ipc/test_ipc.html

In the short term, I'll probably add a suppression so the tree is green, but it would be good if these leaks were fixed. Unlike bug 1219369, it seems like this may not be a singleton data structure leaking, but rather something that may leak more and more the longer we run, so it looks worse.

	Andrew McCreight [:mccr8] Reporter
	Comment 1 • 9 years ago

This is showing up on Win7 and Win8 M2 debug, but not WinXP.

	Andrew McCreight [:mccr8] Reporter
	Comment 2 • 9 years ago

Since we don't run any of the usual Windows e10s debug tests aside from this, this may just be a general problem with e10s on Windows, and not something specific to test_ipc.html.

	Andrew McCreight [:mccr8] Reporter
	Comment 3 • 9 years ago

I filed bug 1219919 for the suppression.