summaryrefslogtreecommitdiffstats
path: root/webkit/webkit.gyp
diff options
context:
space:
mode:
authorukai@chromium.org <ukai@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-04-21 06:50:53 +0000
committerukai@chromium.org <ukai@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-04-21 06:50:53 +0000
commit10821128cb8b272856d1df04fdf102f1dda1b3f2 (patch)
tree1c6fc06244c0f77dccd0317749372bf7b78e93ce /webkit/webkit.gyp
parent13fd6d127b9455f21cc045af9f2f65bf7bca0257 (diff)
downloadchromium_src-10821128cb8b272856d1df04fdf102f1dda1b3f2.zip
chromium_src-10821128cb8b272856d1df04fdf102f1dda1b3f2.tar.gz
chromium_src-10821128cb8b272856d1df04fdf102f1dda1b3f2.tar.bz2
Don't process the same address for websocket throttling.
Host resolver might return address list that contains the same address twice or more. In this case, we should not process the address for websocket throttling multiple times. If we don't have duplicate check of address, it would put the job throttle by the job itself (deadlock). I think this is cause of failure in Linux perf (webkit.org) bot and websocket fail to connect localhost on ubuntu (crbug.com/36652) BUG=36652,41319,40995 TEST=none Review URL: http://codereview.chromium.org/1750001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45156 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit/webkit.gyp')
0 files changed, 0 insertions, 0 deletions