1. Launch Safari
2. Run WebKit.exe /newProcess. Note in Task Manager that only one Safari process is running.
3. Run WebKit.exe foo /newProcess. Note in Task Manager that two Safari processes are now running.
It looks like the first argument that's passed to WebKit.exe is not sent to Safari correctly. I think we're misusing the CreateProcess API.
*** Bug 63389 has been marked as a duplicate of this bug. ***
Created attachment 121296 [details]
Stop using explicit memory management in WebKitLauncherWin
Created attachment 121297 [details]
Prepend Safari.exe's path to the command-line passed to CreateProcess
Committed r104190: <http://trac.webkit.org/changeset/104190>