GLInProcessContext must ensure whether CommandBuffer loses context.
commit41482cb6b6429f5a5e8721bc9163582372cd5f41
authordongseong.hwang@intel.com <dongseong.hwang@intel.com@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 10 Jul 2013 07:35:13 +0000 (10 07:35 +0000)
committerdongseong.hwang@intel.com <dongseong.hwang@intel.com@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 10 Jul 2013 07:35:13 +0000 (10 07:35 +0000)
tree973d72304dd1de90645206d7cca495f2fa1ebddd
parent9ba7c998f6dfa3a54b25a3a69fbdde82063098d4
GLInProcessContext must ensure whether CommandBuffer loses context.

GLInProcessContext plays a similar role to GpuCommandBufferStub in InProcess
mode. GpuCommandBufferStub always ensures whether CommandBuffer loses context via
GpuCommandBufferStub::MakeCurrent(). However, GLInProcessContextImpl does not
have the similar routine. So, when the context is lost,
GLInProcessContextImpl::PumpCommands() pushes ahead GpuScheduler::PutChanged()
although GpuCommandBufferStub stops to run the scheduler.

This patch makes GLInProcessContextImpl stop to run the scheduler if the context
is lost.

TEST=GLRendererTestSyncPoint.SignalSyncPointOnLostContext in cc_unittests
BUG=258007

Review URL: https://chromiumcodereview.appspot.com/18614006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@210776 0039d316-1c4b-4281-b951-d872f2087c98
gpu/command_buffer/client/gl_in_process_context.cc