DevTools/e10s: Difference between revisions

Jump to navigation Jump to search
Line 38: Line 38:
==== Further Analysis ====
==== Further Analysis ====


* Get the remote debugging protocol server running in content processes, and listing tabs hosted in that process.  Should be able to manually connect a debugger to a specific content process (over TCP) and debug that without involvement from the chrome process.
* Figure out and build the transport layer between the chrome and content protocol implementations (IPDL?).


* Figure out and build the transport layer between the chrome and content protocol implementations (IPDL?).
* Get the remote debugging protocol server running in content processes, and listing tabs hosted in that process, proxied through the chrome process but without the protocol forwarding bits.


==== Implementation ====
==== Implementation ====
Confirmed users
673

edits

Navigation menu