Oh, i forgot to mention that firefox takes about a gigabyte of memory
after having stalled at 200mb parsed in a 330mb document..
And despite using setTimeout(), firefox frequently freezes (for about
2 to 10 minutes), before updating the decoding-status display again.
I'd really appreciate
Rene Veerman wrote:
Oh, i forgot to mention that firefox takes about a gigabyte of memory
after having stalled at 200mb parsed in a 330mb document..
And despite using setTimeout(), firefox frequently freezes (for about
2 to 10 minutes), before updating the decoding-status display again.
Op 1/28/10 5:03 PM, Rene Veerman schreef:
Oh, i forgot to mention that firefox takes about a gigabyte of memory
after having stalled at 200mb parsed in a 330mb document..
And despite using setTimeout(), firefox frequently freezes (for about
2 to 10 minutes), before updating the
On Thu, 2010-01-28 at 17:30 +0100, Jochem Maas wrote:
Op 1/28/10 5:03 PM, Rene Veerman schreef:
Oh, i forgot to mention that firefox takes about a gigabyte of memory
after having stalled at 200mb parsed in a 330mb document..
And despite using setTimeout(), firefox frequently freezes
At 200Mb/330Mb parsing, i have released 200Mb of html comment nodes,
and should have accumulated only 200Mb of javascript array/object.
it's _just_ the data, no HTML has been generated yet.
I accept a 5x overhead for turning it into HTML, but wonder why
firefox
a) stops updating the screen despite
On Thu, Jan 28, 2010 at 5:32 PM, Ashley Sheridan
a...@ashleysheridan.co.ukwrote:
You could page through the data and make it look like it's happening all in
the browser with a bit of clever ajax
Ok, good point.
Maybe JSON-transport javascript parsing just has it's limit at just over
100
6 matches
Mail list logo
