Platform/Integration/InjectEject/Launcher Process/: Difference between revisions

Platform/Integration/InjectEject/Launcher Process/ (view source)

5 bytes added , 24 July 2019

no edit summary

98

edits

@@ Line 38: / Line 38: @@
 '''''Why does the Launcher Process not wait for the browser by default?'''''
-* Over the course of a Firefox browsing session, the launcher process lies dormant and its private virtual memory would eventually be paged out to disk. However, it would still be visible as yet another <code>firefox.exe</code> process in the operating system's process list.
+* Over the course of a Firefox browsing session, the launcher process would lie dormant and its private virtual memory would eventually be paged out to disk. However, it would still be visible as yet another <code>firefox.exe</code> process in the operating system's process list.
 ** To avoid the launcher process being charged against Firefox's overall resource usage (and the public perceptions that doing so would entail), we let the launcher process exit.
 ** We also do not want launcher process VM to be unnecessarily occupying space in the page file on machines where there is limited page file space. This is not uncommon - see our various OOM crash reports if you don't believe it!