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 event loop. -atw On Wed, Aug 12, 2009 at 3:31 PM, Jeremy Orlow <[email protected]> wrote: > 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 PM, Darin Fisher <[email protected]> wrote: > >> 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 <[email protected]>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 the JSC "timeoutChecker" mechanism to >>> halt script execution. Is there an analog we can use for V8? >>> >>> I didn't see anything that looked particularly likely from a quick browse >>> through the v8 headers, and I also didn't see anything similar for page >>> script in V8Proxy.cpp, so I'm obviously missing something since page script >>> handles infinite loops gracefully. >>> >>> -atw >>> >>> >>> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
