98
edits
Platform/Integration/InjectEject/Launcher Process/: Difference between revisions
Platform/Integration/InjectEject/Launcher Process/ (view source)
Revision as of 21:44, 24 July 2019
, 24 July 2019no edit summary
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
* It must recover gracefully from failures; | * It must recover gracefully from failures; | ||
* Its code must be self-contained inside <code>firefox.exe</code>; | * Its code must be self-contained inside <code>firefox.exe</code>; | ||
* Its code cannot start nor rely on prefs, XPCOM, <code>nsString</code>, crash reporter, or other aspects of the Gecko runtime. Header-only code that does not depend on <code>xul.dll</code> (such as MFBT) is safe to use in the launcher process; | * Its code cannot start nor rely on prefs, XPCOM, <code>nsString</code>, crash reporter, or other aspects of the Gecko runtime. Header-only code that does not depend on <code>xul.dll</code> (such as most of MFBT) is safe to use in the launcher process; | ||
* Some parts of its code must be freestanding -- that is, those parts cannot assume the presence of either the C runtime or the Win32 API. | * Some parts of its code must be freestanding -- that is, those parts cannot assume the presence of either the C runtime or the Win32 API. | ||