summaryrefslogtreecommitdiffstats
path: root/ios/consumer/base
diff options
context:
space:
mode:
authordalecurtis@chromium.org <dalecurtis@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-11-28 05:51:57 +0000
committerdalecurtis@chromium.org <dalecurtis@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-11-28 05:51:57 +0000
commitdd868dcc5094fa78af7ff05262e12eb8f1fef78a (patch)
tree86f33054c8e2b27c3ec52eb6ea6f5d13a5c90155 /ios/consumer/base
parent8521065bd5bd996225e93e8443ee9082d4433cdd (diff)
downloadchromium_src-dd868dcc5094fa78af7ff05262e12eb8f1fef78a.zip
chromium_src-dd868dcc5094fa78af7ff05262e12eb8f1fef78a.tar.gz
chromium_src-dd868dcc5094fa78af7ff05262e12eb8f1fef78a.tar.bz2
Don't start WASAPI render thread until setup completes.
Creating the render thread before setting up the |audio_client_| may lead to race conditions when repeatedly starting and stopping a stream. With this patch, nothing touches |audio_client_| until IAudioClient triggers the render event for data. As a bonus, it fixes a destruction issue where |audio_clock| was being destructed on the wrong thread (render vs audio), see docs: http://msdn.microsoft.com/en-us/library/windows/desktop/dd370873.aspx BUG=310838 TEST=none Review URL: https://codereview.chromium.org/89663004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@237694 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ios/consumer/base')
0 files changed, 0 insertions, 0 deletions