diff options
| author | davej@google.com <davej@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-07-20 19:47:46 +0000 |
|---|---|---|
| committer | davej@google.com <davej@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-07-20 19:47:46 +0000 |
| commit | 1fec68cf0726faf2d2e7641fab0d01bbd9f7555a (patch) | |
| tree | cc88881d5fd7bcea20809a0e35e73e041568ee7d /chrome/browser/parsers/metadata_parser_filebase.cc | |
| parent | 4f30f9259d990c5efc2d2417cb0898cbf3b9eec7 (diff) | |
| download | chromium_src-1fec68cf0726faf2d2e7641fab0d01bbd9f7555a.zip chromium_src-1fec68cf0726faf2d2e7641fab0d01bbd9f7555a.tar.gz chromium_src-1fec68cf0726faf2d2e7641fab0d01bbd9f7555a.tar.bz2 | |
In an attempt to clear up the Issue 48553 memory leak during init, I re-ordered some of the
startup calls, most important being to call pa_threaded_mainloop_start() right away instead
of after further calls, and creating pa_context_ while the lock was held.
BUG=48553
TEST=See if Valgrind stops suppressing 48553
Review URL: http://codereview.chromium.org/2948013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@53081 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/parsers/metadata_parser_filebase.cc')
0 files changed, 0 insertions, 0 deletions