Fix issue 11006 - any plugin process started by InProcessBrowserTest was...

Fix issue 11006 - any plugin process started by InProcessBrowserTest was
using the unit_test executable rather than chrome.exe.  This patch repurposes
the --renderer-path switch to be --browser-subprocess-path for both plugins and
renderers.  

BUG=11006
TEST=Any InProcessBrowserTest (they all will start at least one renderer). Use
NavigateToURL to a URL containing flash, we shouldn't crash.



Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=14951

[jcampan, 2009-04-24 23:49:56]

I don't see the InProcbrowserTest class specifying the new parameter. How is it
specified to the browser so that plugin_process_host.cc can retrieve it?

http://codereview.chromium.org/99011/diff/1/5
File chrome/common/chrome_switches.cc (right):

http://codereview.chromium.org/99011/diff/1/5#newcode69
Line 69: // Path to the exe to run for the renderer subprocess
Comment should mention it is for plugins as well.

[tim (not reviewing), 2009-04-25 00:14:20]

Oops! Forgot to include the file in the patch!
Also fixed comment.

On 2009/04/24 23:49:56, jcampan wrote:
> I don't see the InProcbrowserTest class specifying the new parameter. How is
it
> specified to the browser so that plugin_process_host.cc can retrieve it?
> 
> http://codereview.chromium.org/99011/diff/1/5
> File chrome/common/chrome_switches.cc (right):
> 
> http://codereview.chromium.org/99011/diff/1/5#newcode69
> Line 69: // Path to the exe to run for the renderer subprocess
> Comment should mention it is for plugins as well.

[jcampan, 2009-04-25 00:30:17]

LGTM