98
edits
Platform/Integration/InjectEject/Launcher Process/: Difference between revisions
Platform/Integration/InjectEject/Launcher Process/ (view source)
Revision as of 21:38, 24 July 2019
, 24 July 2019→Considerations for Developers: Added -launcher command line option
(→Dropping Full Administrator Privileges: Some touch-ups) |
(→Considerations for Developers: Added -launcher command line option) |
||
| Line 45: | Line 45: | ||
== Considerations for Developers == | == Considerations for Developers == | ||
* The launcher process is enabled by default both in local and CI builds. It may be disabled by specifying the <code>--disable-launcher-process</code> option in <code>mozconfig</code>. Leaving this as its default is preferred to ensure that the launcher process receives just as much testing as our other processes. | * The launcher process is enabled by default both in local and CI builds. It may be disabled by specifying the <code>--disable-launcher-process</code> option in <code>mozconfig</code>. Leaving this as its default is preferred to ensure that the launcher process receives just as much testing as our other processes. | ||
** If you have disabled the launcher process by default in your local build, but would like to run it during a test, use the <code>-launcher</code> command-line option. | |||
* Both <code>mach run</code> and <code>mach gtest</code> automatically specify the <code>-wait-for-browser</code> option when starting Firefox. Visual Studio projects generated by the build system also automatically include this flag when running Firefox. | * Both <code>mach run</code> and <code>mach gtest</code> automatically specify the <code>-wait-for-browser</code> option when starting Firefox. Visual Studio projects generated by the build system also automatically include this flag when running Firefox. | ||
* Developers using the Visual Studio Debugger should install the [https://devblogs.microsoft.com/devops/introducing-the-child-process-debugging-power-tool/ Child Process Debugging Power Tool] to enable the debugger to attach to multiple processes simultaneously. | * Developers using the Visual Studio Debugger should install the [https://devblogs.microsoft.com/devops/introducing-the-child-process-debugging-power-tool/ Child Process Debugging Power Tool] to enable the debugger to attach to multiple processes simultaneously. | ||