diff options
| author | paulg@google.com <paulg@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-08-01 00:14:02 +0000 |
|---|---|---|
| committer | paulg@google.com <paulg@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-08-01 00:14:02 +0000 |
| commit | 1ca6df9ae9d23bffa27bb1f5fd19a79a6621939a (patch) | |
| tree | a9fea3767e301099e4343fd228209df02143130f /chrome/browser/page_state.h | |
| parent | 656e3b3857e315a4a6386944fb140ef202580f77 (diff) | |
| download | chromium_src-1ca6df9ae9d23bffa27bb1f5fd19a79a6621939a.zip chromium_src-1ca6df9ae9d23bffa27bb1f5fd19a79a6621939a.tar.gz chromium_src-1ca6df9ae9d23bffa27bb1f5fd19a79a6621939a.tar.bz2 | |
Eliminate the infinite read loop that can occasionally allow
a large, fast network request to monopolize the IO thread.
This particular bug was tickled by an FTP download where
pause tasks posted to the IO thread from the UI thread were
blocked from running until the FTP transfer was completed,
leading to user noticeable jankiness.
I added histograms to the previous read loop and noticed
that during regular browsing and downloading sessions, the
number of times the loop was traversed was 1 for something
like 99.5% of the time. This leads me to believe that
eliminating the read loop in favor of asynchronous tasks
will not impact performance.
BUG=1270179
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/page_state.h')
0 files changed, 0 insertions, 0 deletions