2009/8/12 Drew Wilson :
> Hi all,
> It appears from looking at the worker code that if worker script enters into
> an infinite loop, the associated worker thread/process will never exit. The
> JavaScriptCore implementation uses the JSC "timeoutChecker" mechanism to
> halt script execution. Is ther
Correct. This is part of implementing the "kill a worker" part of the
WebWorker specification:
http://www.whatwg.org/specs/web-workers/current-work/#kill-a-worker
The intent is to shutdown workers silently when appropriate, but this
currently relies on the worker thread eventually returning to the
An infinite running script in a worker should be a valid use case.
Computing Pi to the infiniteth digit is actually the first example in the
worker spec, IIRC.
So this would just kill/timeout shared workers that no longer are connected
to any active pages, right?
J
On Wed, Aug 12, 2009 at 3:25 P
I assume we will just kill the slow worker without prompting the user,
right? Please no slow script dialogs.
-Darin
On Wed, Aug 12, 2009 at 12:58 PM, Drew Wilson wrote:
> Hi all,
> It appears from looking at the worker code that if worker script enters
> into an infinite loop, the associated
Ah, my mistake was in believing that page script handles this gracefully -
after running some tests, I see that we must just allow killing the process
:)
OK, thanks.
-atw
On Wed, Aug 12, 2009 at 1:23 PM, Dean McNamee wrote:
> Mads is working on something for this.
>
> On Wed, Aug 12, 2009 at 12
Mads is working on something for this.
On Wed, Aug 12, 2009 at 12:58 PM, Drew Wilson wrote:
> Hi all,
> It appears from looking at the worker code that if worker script enters into
> an infinite loop, the associated worker thread/process will never exit. The
> JavaScriptCore implementation uses t
