The current code (listed below) has been now in use in the Stackoverflow javascript chat room for a while and so far the toughest problem was Array(5000000000).join(“adasdadadasd”) instantly crashing some browser tabs for me when I was running the code executor bot. Monkeypatching Array.prototype.join seems to have fixed this and the maximum execution time of … Read more
ES2015 modules in Workers are available in Safari and in Chromium browsers. If other browsers / versions are your target, you still need to use importScripts(). When available, you create a module-worker like this: new Worker(“worker.js”, { type: “module” }); See: https://html.spec.whatwg.org/#module-worker-example These are the bug-reports for each browser: Firefox: In development (almost done) š … Read more
Even though the Worker works on an other thread than the one of your main page, and can thus run continuously without blocking the UI, it still runs on a single thread. This means that until your sort algorithm has finished, the Worker will delay the execution of the message event handler; it is as … Read more
The best is probably to generate a simple worker-script dynamically, which will internally call importScripts(), which is not limited by this cross-origin restriction. To understand why you can’t use a cross-domain script as a Worker init-script, see this answer. Basically, the Worker context will have its own origin set to the one of that script. … Read more
For Angular 7, see answer below. I spent a lot of time to figure out how to do it, so I hope this can help someone. Preconditions Iām assuming that you have an Angular project (version 2 or 4) generated with Angular CLI 1.0 or higher. It is not mandatory to generate the project with … Read more
Yes, the message queue will have higher importance than timeouts one, and will thus fire at higher frequency. You can bind to that queue quite easily with the MessageChannel API: let i = 0; let j = 0; const channel = new MessageChannel(); channel.port1.onmessage = messageLoop; function messageLoop() { i++; // loop channel.port2.postMessage(“”); } function … Read more
There are a few reasons why the error that you mention could have been thrown, the reasons are listed here. When sending objects to web workers, the object is serialized, and later deserialized in the web worker if the object is a serializable object. This means that the methods for the objects you send to … Read more
Web workers only have access to the following: XMLHttpRequest Application Cache Create other web workers navigator object location object setTimeout method clearTimeout method setInterval method clearInterval method Performance object (mark,measure,now methods: caniuse?) IndexedDB API (see: caniuse?) importScripts method JSON Worker The window or parent objects are not accessible from a Web worker therefore you can’t … Read more
Small update, as the question is now more than half a year old: In Chrome/Chromium 6 you can now send a canvas’ ImageData object to a web worker, let the web worker make changes to the object and then write it back to the canvas using putImageData(..). Google’s Chromabrush does it this way, the source-code … Read more
Alright, I did some more research with the information @Bergi provided and found the following discussion on W3C mailing list: http://w3-org.9356.n7.nabble.com/Limited-DOM-in-Web-Workers-td44284.html And the excerpt that answers why there is no access to the XML parser or DOM parser in the Web Worker: You’re assuming that none of the DOM implementation code uses any sort of … Read more