Closed Bug 1096614 Opened 10 years ago Closed 8 years ago

Make the CCAnalyzer work with e10s

Categories

(Testing :: Mochitest, defect, P3)

defect

Tracking

(e10s+)

RESOLVED WONTFIX
Tracking Status
e10s + ---

People

(Reporter: mccr8, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Whiteboard: [MemShrink:P2])

Attachments

(1 file)

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.
tracking-e10s: --- → ?
Whiteboard: [MemShrink]
Is this something you'd like to look at, Tim?  I think I can work on it if not.
Flags: needinfo?(ttaubert)
(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.
Flags: needinfo?(ttaubert)
Blocks: 1073352
Component: General → Mochitest Chrome
Whiteboard: [MemShrink] → [MemShrink:P2]
e10s test issue.
No longer blocks: 1073352
Depends on: 1073352
Depends on: 1148156
Depends on: 1148163
Depends on: 1149297
Depends on: 1150746
Assignee: nobody → continuation
Priority: -- → P3
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
Closed: 8 years ago
Resolution: --- → WONTFIX
Component: Mochitest Chrome → Mochitest
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: