On Fri, Jan 15, 2010 at 11:47 AM, Jens Alfke <s...@google.com> wrote:
> On Fri, Jan 15, 2010 at 10:20 AM, Rryk <rryk...@gmail.com> wrote:
>
> I am implementing 3D rendering engine for Chromium and I need to
>> download huge scenes via Ajax. However I've noticed that asyncronous
>> Ajax requests are limited to 7-8 MB in size. If I try to download more
>> -- tab crashes (and in --single-process-mode everything crashes in
>> onNoMemory function).
>> Synchronous requests work better -- I was able to download 100M file,
>> but the browser footprint in memory grew like a monster -- it took a
>> whole of 3GB to download a single 100M file. Interesting enough that
>> after downloading it it remained to take all this place. Does it make
>> 30 copies out of it? There should be something wring with it. I am
>> using jQuery for ajax and the code is here http://tinypaste.com/6f7d9.
>>
>
>
What version of Chromium are you using on what OS? Given that you mentioned
3GB of memory, I'm guessing this is a 64 bit system? What's the content of
the payload (i.e. text, binary, some special encoding)?
Synchronous requests are going to be terrible, memory wise. The whole
thing's buffered in the browser process due to some code structure issues.
You should not be doing this anyway - it's really bad for the users to have
the page locked up while a 100MB download occurs.
- James
> These sound like known issues with XMLHTTPRequest and tcmalloc that were
> fixed a few months ago by James Robinson. What version of Chrome are you
> using? This should be fixed in any build from December or later.
>
> (Also, which OS? The tcmalloc issue only affected Windows, IIRC.)
>
> —Jens
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
