| Issue 37518: | Limited number of WebWorkers | |
| 12 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Chrome Version : 4.0.249.89 (Official Build 38071) URLs (if applicable) : Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari 4: Firefox 3.x: OK IE 7: IE 8: What is the expected result? I should be able to create and run as many web workers as I want. What happens instead? On a freshly started Chrome, I can create 16 web workers that work as they should. The 17th never replies. Try opening the attached html file. Every click on the Work! button creates a web worker. The web worker simply posts back the event.data. Note that every time it logs "Running X", the web worker will respond and we log "Finished X". But only 16 times. Then the new web workers don't seem to run any more (or at least, they don't post anything back). Looking in Process Explorer, I can see that every new worker spawns a new process, but only up to 16. I try to terminate the workers with both close() inside the worker and worker.terminate() from the main thread. Neither changes the behaviour.
Jul 18, 2010
#1
claudio....@gmail.com
Jul 19, 2010
To clarify: I do not get an error code. The worker just doesn't start. And the workers seem to leak. Even if I close and reopen the tab (or try to create a worker in another tab), I still have the same problem. Looks like a bug to me.
Jul 19, 2010
Can't reproduce on 5.0.375.99. I guess it is fixed.
Jul 20, 2010
Nope. 5.0.375.99 still does not permit to spawn more than 16 workers at *the same time*. I guess there is an imposed limit somewhere. Who knows why. Firefox does not have this issue.
Jun 10, 2011
I believe this is our limit due to Workers creating a new process which were working on fixing now. We may still have a limit but we should have an error if the Web Worker can't be created in a reasonable amount of time.
Status:
Available
Owner: levin@chromium.org Cc: dslomov@chromium.org levin@chromium.org Labels: -Area-Undefined Area-WebKit OS-All
Jun 14, 2011
(No comment was entered for this change.)
Labels:
Feature-Workers
Aug 1, 2011
When is the fix for this going to make it into production code?
Aug 1, 2011
This bug is still open so there is no fix to make it into any channel yet including production code. It is still in progress and people are working on making it happen as fast as they can.
Dec 7, 2011
You're the best one to resolve this with appropriate information.
Owner:
dslomov@chromium.org
Mar 6, 2012
Available + Owner == Default to Assigned
Status:
Assigned
Mar 10, 2013
(No comment was entered for this change.)
Labels:
-Area-WebKit Cr-Content
Apr 5, 2013
(No comment was entered for this change.)
Labels:
-Cr-Content Cr-Blink
Apr 15, 2015
(No comment was entered for this change.)
Labels:
Cr-Blink-JavaScript-Language
Apr 16, 2015
What is the status of this bug? I've modified the sample in the description to keep workers alive by removing close/terminate calls. On Ubuntu, I was able to get to 50 workers before the tab crashed, and on Windows about 150. On OS X, I got all the way to 250 workers and gave up as Chrome was starting to slow down. I did not observe worker starvation in any tests I tried. 41.0.2272.118; Ubuntu and OS X 64-bit builds, and 32-bit on Windows. |
||||||||
| ► Sign in to add a comment | |||||||||
