summaryrefslogtreecommitdiffstats
path: root/ui/gfx/screen_aura.cc
diff options
context:
space:
mode:
authorapatrick@chromium.org <apatrick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-12-08 01:58:52 +0000
committerapatrick@chromium.org <apatrick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-12-08 01:58:52 +0000
commit076a24061afba53710991ac5be1d42d54df566fb (patch)
treec7ae6ac57f5e5b63e38ecc82ca36012137696592 /ui/gfx/screen_aura.cc
parent19b4a024c89bed91b19e7573ea67f1bb9b38012d (diff)
downloadchromium_src-076a24061afba53710991ac5be1d42d54df566fb.zip
chromium_src-076a24061afba53710991ac5be1d42d54df566fb.tar.gz
chromium_src-076a24061afba53710991ac5be1d42d54df566fb.tar.bz2
Win AcceleratedSurface no longer polls queries on separate thread.
This is basically a reversion of the final patch set (#4) of this: http://codereview.chromium.org/8395012 The reason is because tasks posted to the query thread can extend the lifetime of the D3D device such that it is destroyed on the query thread. The D3D thread must be destroyed on the thread it was created on though. The suggestion was a good one and I might revisit it in the future. I also added a missing lock and switched it to load the D3D9 DLL rather than assume it is already loaded by something else. Review URL: http://codereview.chromium.org/8867005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@113529 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ui/gfx/screen_aura.cc')
0 files changed, 0 insertions, 0 deletions