diff options
| author | wtc@google.com <wtc@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-11-14 00:22:51 +0000 |
|---|---|---|
| committer | wtc@google.com <wtc@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-11-14 00:22:51 +0000 |
| commit | a4fb51b3a5e6c541d1d840c32c57dbf1c09345c0 (patch) | |
| tree | fc09612fc8cb675b9b11098e879796dbdc578f09 /chrome/browser/task_manager.h | |
| parent | a95b6ebeb94363671433029e97a488bccb17ff17 (diff) | |
| download | chromium_src-a4fb51b3a5e6c541d1d840c32c57dbf1c09345c0.zip chromium_src-a4fb51b3a5e6c541d1d840c32c57dbf1c09345c0.tar.gz chromium_src-a4fb51b3a5e6c541d1d840c32c57dbf1c09345c0.tar.bz2 | |
A minor tweak of r5245. I'm more confident that WinHTTP
knows a transaction is complete when WinHttpReadData returns
a zero byte count. So it's safer to NOT notify the request
throttle when WinHttpReadData returns a nonzero byte count,
even if we have read the number of bytes specified in the
Content-Length response header. I verified that this is
still enough to fix the bug (unresponsiveness).
R=darin
BUG=4302
Review URL: http://codereview.chromium.org/10867
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@5415 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/task_manager.h')
0 files changed, 0 insertions, 0 deletions