1586539 - Attach to processes for OOP iframes when debugging a browsing context

Status: RESOLVED DUPLICATE of bug 1626655

(DevTools :: Debugger, enhancement, P2)

Description

[Brian Hackett [Laid off!]]

Attachment: screenshot.png

With the changes in bug 1580168, when debugging a tab the debugger client can match up the pids returned by listProcesses() with the pids associated with the remote frames of the target tab. This allows the debugger to attach to those processes associated with its target, even when not using the OBT. With the changes in bug 1586359 and bug 1586468, the content processes listed will update as iframes are added or removed.

Comment 1

[Brian Hackett [Laid off!]]

Attachment: Bug 1586539 - Attach to processes for OOP iframes when debugging a browsing context, r=jlast.

Comment 2

[Chris Peterson [:cpeterson]]

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Comment 3

[Chris Peterson [:cpeterson]]

Blocks enabling Fission in Nightly (M6).

Comment 4

[Alexandre Poirot [:ochameau]]

bug 1626655 is going to accomplish this. By migrating the Debugger to the TargetList, the Debugger will be debugging all targets kinds the same way, including OOP frames.