Open Bug 1531055 Opened 5 years ago Updated 2 years ago

DebuggerServer should be destroyed after frame is disconnected only when started by frame script

Categories

(DevTools :: General, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: jdescottes, Unassigned)

References

Details

Attachments

(1 obsolete file)

Follow up to Bug 1528276.

We need a clean way to check if a DebuggerServer should be destroyed when all connections to target frames have been lost.

The feature was initially intended in order to cleanup Content Process debugger servers, but not all servers used by DevTools frame script have the same role. For instance for Fennec, we only have a single DebuggerServer (non-e10s...) so the server used by the frame scripts is the same as the one listening for incoming remote debugging connections.

Some options:

  • only destroy the DebuggerServer when connections are closed if we are in a ContentProcess or if we are using a CustomLoader (which means loaded in the Main Process but in a dedicated sandbox, to debug Chrome pages)
  • frame script could check if the server is already initialized before calling init()
Attachment #9047091 - Attachment is obsolete: true
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: