summaryrefslogtreecommitdiffstats
path: root/chrome/app/google_chrome_strings.grd
diff options
context:
space:
mode:
authordavej@chromium.org <davej@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-07-28 19:19:54 +0000
committerdavej@chromium.org <davej@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-07-28 19:19:54 +0000
commit59e30246acc31440592eaff4ad68b32dcf67360e (patch)
tree4fef44ce2c10448e7fe8a7f6bf7772516f65dded /chrome/app/google_chrome_strings.grd
parentad2362c46b65dcfd8adc46092dda3e5db3781063 (diff)
downloadchromium_src-59e30246acc31440592eaff4ad68b32dcf67360e.zip
chromium_src-59e30246acc31440592eaff4ad68b32dcf67360e.tar.gz
chromium_src-59e30246acc31440592eaff4ad68b32dcf67360e.tar.bz2
An earlier check-in (r51786, Issue 2769008) caused a memory leak on the build bots when PulseAudio was initialized on a separate worker thread. This change calls PulseAudioMixer::InitSync() so the init happens on the calling thread. For some reason, the init finishes cleanly on one thread, but not the other.
BUG=48553 (and http://code.google.com/p/chromium-os/issues/detail?id=5141) TEST=Valgrind should not have PulseAudio related memory leaks, suppression 48553, or assertion failures. Review URL: http://codereview.chromium.org/3026028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@53992 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/app/google_chrome_strings.grd')
0 files changed, 0 insertions, 0 deletions