From what I'm seeing in bug 1094749, it looks like we're running the CCAnalyzer in the parent process, but not in the child process. These debugger tests are creating and destroying windows in the child process, so we need to run in there, too, maybe even only there.
Is this something you'd like to look at, Tim? I think I can work on it if not.
(In reply to Andrew McCreight [:mccr8] from comment #1) > Is this something you'd like to look at, Tim? I think I can work on it if > not. Sorry I think I can't pick this up anytime soon but I can give feedback if that helps.
e10s test issue.
tracking-e10s: ? → +
Created attachment 8587750 [details] [diff] [review] Run the CC checker in ShutdownLeakChecker. WIP.
try run, showing a leak still: https://treeherder.mozilla.org/#/jobs?repo=try&revision=2b5bc67e4bd3
I'm not sure if this is worth fixing, or the dependent bugs. We may want to just remove the CCAnalyzer.
Assignee: continuation → nobody
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
Component: Mochitest Chrome → Mochitest
Product: Testing → Testing
You need to log in before you can comment on or make changes to this bug.