summaryrefslogtreecommitdiffstats
path: root/app
diff options
context:
space:
mode:
authorananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-10-24 01:29:20 +0000
committerananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-10-24 01:29:20 +0000
commit5778de6e6bfbc0439f49a245a75efa44e4f9a771 (patch)
tree7596aff0328ee022a23a9a0e84c28f94ee40ea30 /app
parentb5be3f53d7af0037dbc634beb550752de56ad840 (diff)
downloadchromium_src-5778de6e6bfbc0439f49a245a75efa44e4f9a771.zip
chromium_src-5778de6e6bfbc0439f49a245a75efa44e4f9a771.tar.gz
chromium_src-5778de6e6bfbc0439f49a245a75efa44e4f9a771.tar.bz2
Currently the host network stack in IE which uses Urlmon interfaces to initiate
and complete URL downloads requested by ChromeFrame, executes in the UI thread of IE. While this works fine in most cases for large data sizes, the IE UI thread ends up being busy pulling the data in our IBindStatusCallback::OnDataAvailable implementation. As a result the browser hangs until all data is pulled out. The fix is to handle Urlmon requests on a separate thread. This fixes http://code.google.com/p/chromium/issues/detail?id=24007 Changes to plugin_url_request.cc/.h are to set the LF property on these files. Bug=24007 Review URL: http://codereview.chromium.org/292035 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@29986 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'app')
0 files changed, 0 insertions, 0 deletions