{"action":"created","issue":{"url":"https://api.github.com/repos/whatwg/html/issues/319","labels_url":"https://api.github.com/repos/whatwg/html/issues/319/labels{/name}","comments_url":"https://api.github.com/repos/whatwg/html/issues/319/comments","events_url":"https://api.github.com/repos/whatwg/html/issues/319/events","html_url":"https://github.com/whatwg/html/issues/319","id":115827774,"number":319,"title":"Detecting working allocation failure","user":{"login":"annevk","id":1544111,"avatar_url":"https://avatars.githubusercontent.com/u/1544111?v=3","gravatar_id":"","url":"https://api.github.com/users/annevk","html_url":"https://github.com/annevk","followers_url":"https://api.github.com/users/annevk/followers","following_url":"https://api.github.com/users/annevk/following{/other_user}","gists_url":"https://api.github.com/users/annevk/gists{/gist_id}","starred_url":"https://api.github.com/users/annevk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/annevk/subscriptions","organizations_url":"https://api.github.com/users/annevk/orgs","repos_url":"https://api.github.com/users/annevk/repos","events_url":"https://api.github.com/users/annevk/events{/privacy}","received_events_url":"https://api.github.com/users/annevk/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-11-09T08:07:54Z","updated_at":"2015-11-12T14:19:54Z","closed_at":null,"body":"In https://www.w3.org/Bugs/Public/show_bug.cgi?id=29039 and more prominently in https://bugzilla.mozilla.org/show_bug.cgi?id=1052398 @lukewagner and @lars-t-hansen discuss problems with `Worker` objects getting created but their corresponding workers not getting allocated.\r\n\r\nI'm curious to hear what @kinu, @sof, @travisleithead, @hober, and others think of that. Would it be acceptable to make `new Worker()` throw, should we have a second parameter to opt into that behavior, expose state on `Worker` objects, or something else altogether?"},"comment":{"url":"https://api.github.com/repos/whatwg/html/issues/comments/156113920","html_url":"https://github.com/whatwg/html/issues/319#issuecomment-156113920","issue_url":"https://api.github.com/repos/whatwg/html/issues/319","id":156113920,"user":{"login":"wanderview","id":1256526,"avatar_url":"https://avatars.githubusercontent.com/u/1256526?v=3","gravatar_id":"","url":"https://api.github.com/users/wanderview","html_url":"https://github.com/wanderview","followers_url":"https://api.github.com/users/wanderview/followers","following_url":"https://api.github.com/users/wanderview/following{/other_user}","gists_url":"https://api.github.com/users/wanderview/gists{/gist_id}","starred_url":"https://api.github.com/users/wanderview/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wanderview/subscriptions","organizations_url":"https://api.github.com/users/wanderview/orgs","repos_url":"https://api.github.com/users/wanderview/repos","events_url":"https://api.github.com/users/wanderview/events{/privacy}","received_events_url":"https://api.github.com/users/wanderview/received_events","type":"User","site_admin":false},"created_at":"2015-11-12T14:19:54Z","updated_at":"2015-11-12T14:19:54Z","body":"FWIW, the \"swappable\" concept is similar to what service workers do.  The browser is free to kill the worker thread even though there is a ServiceWorker DOM object alive.  The thread is restarted on demand, etc.\r\n\r\nIt comes with a big caveat for devs not to rely on global state, though."}}