зеркало из https://github.com/mozilla/gecko-dev.git
e4aa62dc2c
Currently when browser chrome tests are failing the open tabs, client, and Remote Agent will never be closed, and as such each failing test causes massive memory leaks. Therefore the teardown logic needs to be moved out of the tests into the "add_task()" function. Only that way we can make sure to run all the clean-up steps independent of the test success state. Differential Revision: https://phabricator.services.mozilla.com/D50233 --HG-- extra : moz-landing-system : lando |
||
---|---|---|
.. | ||
doc | ||
domains | ||
server | ||
sessions | ||
targets | ||
test | ||
.gitignore | ||
Connection.jsm | ||
Error.jsm | ||
JSONHandler.jsm | ||
Log.jsm | ||
Observer.jsm | ||
Protocol.jsm | ||
README | ||
RecommendedPreferences.jsm | ||
RemoteAgent.conf | ||
RemoteAgent.jsm | ||
Sync.jsm | ||
jar.mn | ||
mach_commands.py | ||
moz.build |
README
The Firefox remote agent is a low-level debugging interface based on the CDP protocol. With it, you can inspect the state and control execution of documents running in web content, instrument Gecko in interesting ways, simulate user interaction for automation purposes, and debug JavaScript execution. This component provides an experimental and partial implementation of a remote devtools interface using the CDP protocol and transport layer. See https://firefox-source-docs.mozilla.org/remote/ for documentation. The remote agent is disabled by default, but can be enabled by setting a preference before running it: % ./mach run --setpref "remote.enabled=true" --remote-debugger