diff options
| author | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-06-16 21:32:18 +0000 |
|---|---|---|
| committer | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-06-16 21:32:18 +0000 |
| commit | 8539853434540887affc21d493a2cccbbc4669aa (patch) | |
| tree | d6400054c3f39ac493389c41cbd49569e1908a31 /net/base/tcp_client_socket_pool.cc | |
| parent | f387b35af395c0a636a721b5cef33a46444a0b27 (diff) | |
| download | chromium_src-8539853434540887affc21d493a2cccbbc4669aa.zip chromium_src-8539853434540887affc21d493a2cccbbc4669aa.tar.gz chromium_src-8539853434540887affc21d493a2cccbbc4669aa.tar.bz2 | |
Properly cleanup state after synchronous DNS resolution
Pre-resoultion system was not cleaning up its state when the resolver
returned asynchronously. This regression probably landed when we shifted
to using an internal resolver class, rather than running on worker threads.
The impact was made detectable by the recent introudction of a micro-cache,
which often returns with a synchronous result.
BUG=14212
r=eroman
Review URL: http://codereview.chromium.org/125209
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18537 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/base/tcp_client_socket_pool.cc')
0 files changed, 0 insertions, 0 deletions