Only launch a second un-sandboxed gpu process on Windows.

Only launch a second un-sandboxed gpu process on Windows.

On Linux and Mac, we can do gpu info collection with sandbox on, so no need for a second un-sandboxed gpu process.

BUG=162928
TEST=about:gpu correctly reports sandboxed=true on chromeos
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=171379

[Zhenyao Mo, 2012-12-05 23:26:10]

Al: please review.

[apatrick_chromium, 2012-12-05 23:31:08]

https://codereview.chromium.org/11451021/diff/1/content/gpu/gpu_child_thread.cc
File content/gpu/gpu_child_thread.cc (right):

https://codereview.chromium.org/11451021/diff/1/content/gpu/gpu_child_thread....
content/gpu/gpu_child_thread.cc:177: gpu_info_.sandboxed = sandboxed;
Do any of the implementations of CollectGraphicsInfo actually change
"sandboxed"? If not this line is redundant.

[Zhenyao Mo, 2012-12-05 23:34:11]

https://codereview.chromium.org/11451021/diff/1/content/gpu/gpu_child_thread.cc
File content/gpu/gpu_child_thread.cc (right):

https://codereview.chromium.org/11451021/diff/1/content/gpu/gpu_child_thread....
content/gpu/gpu_child_thread.cc:177: gpu_info_.sandboxed = sandboxed;
On 2012/12/05 23:31:08, apatrick_chromium wrote:
> Do any of the implementations of CollectGraphicsInfo actually change
> "sandboxed"? If not this line is redundant.

CollectGraphicsInfo always reset GPUInfo, so sandboxed will always be false
after the call.

[apatrick_chromium, 2012-12-05 23:35:35]

lgtm