diff options
| author | cbentzel@chromium.org <cbentzel@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-04 14:07:25 +0000 |
|---|---|---|
| committer | cbentzel@chromium.org <cbentzel@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-04 14:07:25 +0000 |
| commit | 86ab0bafce121b61326add8b850da1520c2f4a88 (patch) | |
| tree | 71348366da42d71b9c3595e6e736229d8ec5545c /net | |
| parent | 893858ba3f7b1fee7112fa9bcf778131a64d2230 (diff) | |
| download | chromium_src-86ab0bafce121b61326add8b850da1520c2f4a88.zip chromium_src-86ab0bafce121b61326add8b850da1520c2f4a88.tar.gz chromium_src-86ab0bafce121b61326add8b850da1520c2f4a88.tar.bz2 | |
Remove spammy warning about reaching maximum socket count for the pool.
When I run Chrome through a proxy, this WARNING log triggers very frequently. Typically immediately after it's called, CloseOneIdleSocket() is invoked and a connect job is still allowed to proceed.
If this WARNING was useful in the past, I will add it to the call sites at appropriate places (such as when there are no idle sockets for the pool and a request must be queued) rather than inside ReachedMaxSocketsLimit().
BUG=None
TEST=None
Review URL: http://codereview.chromium.org/3526013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61363 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net')
| -rw-r--r-- | net/socket/client_socket_pool_base.cc | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/net/socket/client_socket_pool_base.cc b/net/socket/client_socket_pool_base.cc index 90cb49a..9b0aa6d 100644 --- a/net/socket/client_socket_pool_base.cc +++ b/net/socket/client_socket_pool_base.cc @@ -833,7 +833,6 @@ bool ClientSocketPoolBaseHelper::ReachedMaxSocketsLimit() const { DCHECK_LE(total, max_sockets_); if (total < max_sockets_) return false; - LOG(WARNING) << "ReachedMaxSocketsLimit: " << total << "/" << max_sockets_; return true; } |