BUG: using .setTimeout() during long js routine causes cripling wa

WTF ppl....

It's troublesome enough that one can't run long js routines with the browser
taking care of the necessary pauses to allow UI updating etc.

For my lgpl http://mediabeez.ws/htmlMicroscope/, i can, with firefox, parse
130 megabyte of JSON data into a nice HTML collapsed-expansible view.
My json parser does not eval() and uses frequent .setTimeout()s.

IE8, whether in compatibility mode or not, will just pop up the "stop
running this script" window, and it also messes up the run-state of the js
engine (probably by only partially halting it), causing my JSON decoder to
fail completely.

I'm afraid you've left me no choice but to post an honest statement about
IE8's failure to run serious javascript.

I would VERY much like to be informed by a M$ engineer about what if
anything "i'm doing wrong".

I must say that i find the quality of your js engine, particularly because
it can't even auto-suspend js for UI updating and other overheadish work, nor
(auto-)attach QOS settings to a js thread to prevent CPU abuse.

In news:7375CDF5-BFE6-4285-B92B-,
rene7705 <> typed:
> WTF ppl....
>
> It's troublesome enough that one can't run long js routines with the
> browser taking care of the necessary pauses to allow UI updating etc.
>
> For my lgpl http://mediabeez.ws/htmlMicroscope/, i can, with firefox,
> parse 130 megabyte of JSON data into a nice HTML collapsed-expansible
> view.
> My json parser does not eval() and uses frequent .setTimeout()s.
>
> IE8, whether in compatibility mode or not, will just pop up the "stop
> running this script" window, and it also messes up the run-state of
> the js engine (probably by only partially halting it), causing my
> JSON decoder to fail completely.
>
> I'm afraid you've left me no choice but to post an honest statement
> about IE8's failure to run serious javascript.
>
> I would VERY much like to be informed by a M$ engineer about what if
> anything "i'm doing wrong".
>
> I must say that i find the quality of your js engine, particularly
> because it can't even auto-suspend js for UI updating and other
> overheadish work, nor (auto-)attach QOS settings to a js thread to
> prevent CPU abuse.

This is usenet, not Microsoft employees.