diff options
| author | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-12-08 21:20:51 +0000 |
|---|---|---|
| committer | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-12-08 21:20:51 +0000 |
| commit | f628e1b444c32ad882a3e57bc0d58170cec716ef (patch) | |
| tree | 3a7fd25a9e5b19e622ddb946c72dbe4c072af820 /testing | |
| parent | ee82ec3dc0180187107c616b3a8c690215350a44 (diff) | |
| download | chromium_src-f628e1b444c32ad882a3e57bc0d58170cec716ef.zip chromium_src-f628e1b444c32ad882a3e57bc0d58170cec716ef.tar.gz chromium_src-f628e1b444c32ad882a3e57bc0d58170cec716ef.tar.bz2 | |
The cache object used by the UrlmonUrlRequest class in ChromeFrame creates an in memory stream, which is used
to hold data received from Urlmon until Chrome reads it. At times attempts to write to this stream fail
with E_OUTOFMEMORY.
We don't really need the complexity of an in memory stream for our cache. A vector of bytes would do just fine.
This fixes bug http://code.google.com/p/chromium/issues/detail?id=28658
I verified that it actually fixes this issue.
Bug=28648
Test=covered by existing net tests.
Review URL: http://codereview.chromium.org/469014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34086 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'testing')
0 files changed, 0 insertions, 0 deletions