Alexandre Poirot 3e4fdd2d31 Bug 1583252 - Shutdown content process DebuggerServer only once the last connection closes. r=jdescottes ... When multiple DebuggerClients starts debugging the same content process target, the first one to close will destroy the other one as we destroy the server and the loader as soon as we receive the debug:content-process-destroy message. We should destroy them only once the last client closes. i.e. when the last connection registered in the content process is destroyed. Differential Revision: https://phabricator.services.mozilla.com/D47661 --HG-- extra : moz-landing-system : lando		2019-10-02 16:24:36 +00:00
..
actors	Bug 1574401 - allow reparenting r=rcaliman,ochameau	2019-10-02 09:49:12 +00:00
connectors	Bug 1583252 - Shutdown content process DebuggerServer only once the last connection closes. r=jdescottes	2019-10-02 16:24:36 +00:00
performance	Bug 1564168 - [jsdbg2] Debugger.prototype.enabled should be removed (part 1). r=jimb	2019-07-16 00:56:19 +00:00
performance-new	Bug 1575682 - Bridge the perf actor so that it can be reused with the popup r=julienw	2019-09-04 20:05:18 +00:00
socket	Bug 1561435 - Format devtools/server/, a=automatic-formatting	2019-07-05 11:26:00 +02:00
startup	Bug 1583252 - Shutdown content process DebuggerServer only once the last connection closes. r=jdescottes	2019-10-02 16:24:36 +00:00
tests	Bug 1583252 - Assert that there is no pending client at end of each test. r=jdescottes	2019-10-02 16:24:29 +00:00
debugger-server-connection.js	Bug 1452920 - Clean up WebConsoleActor events and responses. r=nchevobbe	2019-08-19 06:57:42 +00:00
debugger-server.js	Bug 1583252 - Assert that there is no pending client at end of each test. r=jdescottes	2019-10-02 16:24:29 +00:00
moz.build	Bug 1575682 - Bridge the perf actor so that it can be reused with the popup r=julienw	2019-09-04 20:05:18 +00:00