summaryrefslogtreecommitdiffstats
path: root/chrome/browser/chromeos/bluetooth
diff options
context:
space:
mode:
authorpiman@chromium.org <piman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-03-08 23:46:29 +0000
committerpiman@chromium.org <piman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-03-08 23:46:29 +0000
commit03dc888f5d0e636fd4e55f8f04bb635bfad29b42 (patch)
treeaecd43e4ceb1ba8f9e3bcd3c19a1fd8584489291 /chrome/browser/chromeos/bluetooth
parent10618f2764fb9cfc6fc3cc266d928a9731c0afbc (diff)
downloadchromium_src-03dc888f5d0e636fd4e55f8f04bb635bfad29b42.zip
chromium_src-03dc888f5d0e636fd4e55f8f04bb635bfad29b42.tar.gz
chromium_src-03dc888f5d0e636fd4e55f8f04bb635bfad29b42.tar.bz2
Aura: recover from lost context / GPU process dying
For recovery from lost contexts, we need to: - on the UI thread, recreate the compositing surfaces (since they are textures in the UI compositor context that we lost). - on the IO thread, delay the requests from the renderer process to create view contexts, until the above has happened. BUG=116394,116839 TEST=chrome --ui-use-gpu-process --force-compositing-mode, kill GPU process, check everything still works Review URL: http://codereview.chromium.org/9632005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125727 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/chromeos/bluetooth')
0 files changed, 0 insertions, 0 deletions