Closed Bug 1241485 Opened 9 years ago Closed 9 years ago

Increase the limit for workers per-origin

Categories

(Core :: DOM: Workers, defect)

36 Branch
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla47
Tracking Status
firefox47 --- fixed

People

(Reporter: smaug, Assigned: smaug)

References

Details

(Whiteboard: [games:p1][platform-rel-Games])

Attachments

(3 files)

Attached file a (non-mochi-) test
Currently we limit to 20 per domain (bug 649537) but that is rather low, definitely less than in other browsers. Chrome doesn't seem to have a limit, but it just makes child process crash when around 50 workers are created (linux), or hang for awhile and crash the child process with ~750 workers (Windows). IE11 on Win7 limits to 25, and I was told Edge on Win10 has limit at 25 too. Bug 1052398 is a bit noisy about various different things, so if we just want to make a simple increase to the limit, this is the separate bug for that. I do think any application using lots of workers should be expected to send back a notification from the worker when it is loaded and then it can know how many workers it has to play with. In other words, I'm not really a fan of { throwOnCreation: true } proposal. Based on the behavior Chrome has on linux, I'm proposing we increase the limit to 50. I'll push a patch with a mochitest which creates as many workers as possible to tryserver in order to verify nothing really bad starts to happen if limit is increased.
Should we dupe bug 1222629 to this one?
Attachment #8710576 - Flags: review?(khuey)
Desktop Safari seems to limit to 290 but it is not clear to me what kind of limit that is. Not global and not per domain, but perhaps per top level window or something.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla47
Whiteboard: [games:p1] → [games:p1][platform-rel-Games]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: