Reply to thread

Message

[QUOTE="Thomas 'PointedEars' Lahn, post: 5008422"]
It's _millisecond_, whether it is a long or short time for a browser depends
on several factors.

Your main problem, however, is that your approach is wrong.  By calling
setTimeout() in a loop with the same milliseconds value, you are running
"threads" (for the lack of a better word) at approximately the same time.
This is why the browser becomes unresponsive but does not consider the
script to hang.  Probably the CPU usage of the browser or the tab process
goes through the roof:

While you could run window.setTimeout() (you should use the qualified
reference) with a larger multiple of the loop index as milliseconds value,
this would not solve the problem as threads could still become stacked if
a thread took more time than you defined:

CPU usage (%)
^
100 +                   ,.   ,.
:                 #4|| #5|| â€¦
:         ,----.-----.----.----.
:         | #2 | #3  | #4 | #5 | â€¦
:    ,---------+-----+----+----+----.
:    | #1      | #2  |#3  | #4 | #5 | â€¦
'----+----+----+----+----+----+----+----+----> time (ms)
100  200  300  400  500  600

So you should only run *one* "thread" that does the calculation instead:

window.setTimeout(function() {
for (j = 0; j < 100; j++)
{
/* heavy calculations */
}
}, 10);

which would mean

CPU usage (%)
^
100 +
:
:
:
: ,----------------------------------------.
: | Thread #1: 1 â€¦ 100                     |
'-+------------------------------------------> time (ms)
10