diff options
author | piman@chromium.org <piman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-03-08 01:31:28 +0000 |
---|---|---|
committer | piman@chromium.org <piman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-03-08 01:31:28 +0000 |
commit | d8d97c2224367396e57bc69294beaea7002f1f14 (patch) | |
tree | d244686ba1cde27647c3f430308116303f2e6705 /content/common/gpu/gpu_messages.h | |
parent | 6bba9e85d2c95d8657ebf348e49547ed2622a0c9 (diff) | |
download | chromium_src-d8d97c2224367396e57bc69294beaea7002f1f14.zip chromium_src-d8d97c2224367396e57bc69294beaea7002f1f14.tar.gz chromium_src-d8d97c2224367396e57bc69294beaea7002f1f14.tar.bz2 |
Fix context sharing between channels to be order-independent.
Ensuring order of channel recreation after a GPU process death is very hard.
With this there's not need. A channel is either shared or not, all the "shared"
channels share their context together, every other one doesn't share with
anything. More restrictive but it's enough for our needs.
BUG=116913
TEST=chrome --ui-use-gpu-process, kill GPU process, observe GpuChannelManager::OnEstablishChannel crash doesn't happen.
Review URL: https://chromiumcodereview.appspot.com/9619017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125521 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/common/gpu/gpu_messages.h')
-rw-r--r-- | content/common/gpu/gpu_messages.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/common/gpu/gpu_messages.h b/content/common/gpu/gpu_messages.h index 0b600ab..a8cf142 100644 --- a/content/common/gpu/gpu_messages.h +++ b/content/common/gpu/gpu_messages.h @@ -157,7 +157,7 @@ IPC_MESSAGE_CONTROL0(GpuMsg_Initialize) // This ID is a unique opaque identifier generated by the browser process. IPC_MESSAGE_CONTROL2(GpuMsg_EstablishChannel, int /* client_id */, - int /* share_client_id */) + bool /* share_context */) // Tells the GPU process to close the channel identified by IPC channel // handle. If no channel can be identified, do nothing. |