Chromium Code Reviews| Index: gpu/command_buffer/service/gles2_cmd_decoder.cc |
| diff --git a/gpu/command_buffer/service/gles2_cmd_decoder.cc b/gpu/command_buffer/service/gles2_cmd_decoder.cc |
| index 3fc39c6dda1c29f787f7a8648d00baa58d85d481..6330cf2aa591c50a741df57dbe80d786abff7161 100644 |
| --- a/gpu/command_buffer/service/gles2_cmd_decoder.cc |
| +++ b/gpu/command_buffer/service/gles2_cmd_decoder.cc |
| @@ -3343,6 +3343,15 @@ error::Error GLES2DecoderImpl::DoCommand( |
| return result; |
| } |
| +error::Error GLES2DecoderImpl::HandleLoseContextCHROMIUM( |
| + uint32 immediate_data_size, const gles2::LoseContextCHROMIUM& c) { |
| + // TODO(gman): I suspect it's not this simple. The most common context |
| + // lost event is currently the GPU process crashing which will take down all |
| + // contexts. After that, it seems likely you'd want to lose all contexts in |
| + // the current ContextGroup otherwise you'll likely leak resources. |
|
Ken Russell (switch to Gerrit)
2012/12/15 01:21:28
Yes -- I think the command should lose all context
|
| + return error::kLostContext; |
| +} |
| + |
| void GLES2DecoderImpl::RemoveBufferInfo(GLuint client_id) { |
| buffer_manager()->RemoveBufferInfo(client_id); |
| } |