Windows: On context lost, GPU process exits.

Windows: On context lost, GPU process exits.

Some drivers cannot recover from device lost. IDirect3DDevice9::ResetEx returns an access denied error after a GPU hang. Although this results in a fallback to software, exiting the GPU process allows a newly launched GPU process to reinitialize D3D and GPU accelerated features continue to work.

I have observed this with an AMD driver but suspect there are issues with Intel from crash reports.

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=191705

[Ken Russell (switch to Gerrit), 2013-03-27 02:04:11]

+zmo

lgtm

https://codereview.chromium.org/12617020/diff/5001/gpu/command_buffer/service...
File gpu/command_buffer/service/feature_info.cc (right):

https://codereview.chromium.org/12617020/diff/5001/gpu/command_buffer/service...
gpu/command_buffer/service/feature_info.cc:709:
workarounds_.exit_on_context_lost = true;
It would be much better and more maintainable to set this flag from the GPU
blacklist. Is that feasible?

https://codereview.chromium.org/12617020/diff/5001/gpu/command_buffer/service...
File gpu/command_buffer/service/gles2_cmd_decoder.cc (right):

https://codereview.chromium.org/12617020/diff/5001/gpu/command_buffer/service...
gpu/command_buffer/service/gles2_cmd_decoder.cc:2861: << " a D3D device in the
Chrome GPU process sandbox.";
Consider changing this message to be either more generic or #ifdef'd in the case
that this workaround is used on other OSs.

[Zhenyao Mo, 2013-03-27 02:53:54]

https://codereview.chromium.org/12617020/diff/5001/gpu/command_buffer/service...
File gpu/command_buffer/service/feature_info.cc (right):

https://codereview.chromium.org/12617020/diff/5001/gpu/command_buffer/service...
gpu/command_buffer/service/feature_info.cc:709:
workarounds_.exit_on_context_lost = true;
On 2013/03/27 02:04:11, kbr wrote:
> It would be much better and more maintainable to set this flag from the GPU
> blacklist. Is that feasible?

I just did some refactoring and the mechanism to do this in blacklist is ready. 
I am planning to move all the workarounds to blacklist (I call it driver bug
list).

This CL LGTM as it is.  Land this and I'll work on top of that.

[commit-bot: I haz the power, 2013-04-01 20:06:58]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/apatrick@chromium.org/12617020/21001

[commit-bot: I haz the power, 2013-04-01 23:52:30]

Change committed as 191705