Closed
Bug 1137398
Opened 10 years ago
Closed 10 years ago
disallow creating nested workers from ServiceWorker
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla39
Tracking | Status | |
---|---|---|
firefox39 | --- | fixed |
People
(Reporter: bkelly, Assigned: gioyik, Mentored)
References
Details
(Whiteboard: [good first bug])
Attachments
(1 file)
1.16 KB,
patch
|
bkelly
:
review+
baku
:
review+
|
Details | Diff | Splinter Review |
We should disallow creating nested workers in a ServiceWorker for now. Nesting workers from SW create some interesting footguns:
1) The worker script will not be automatically persisted like the SW script and importScripts(). They would have to manually persist and then use a data URI nested worker. This is perhaps non-intuitive.
2) The lifecylce of the nested worker would be very hard to predict. The ServiceWorker can get shutdown by the UA at almost any time. The dedicated worker would then seemingly get killed randomly as well.
We can fix this by changing Worker.webidl to use:
Exposed=Window,DedicatedWorker,SharedWorker,System
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8570576 -
Flags: review?(bkelly)
Reporter | ||
Comment 2•10 years ago
|
||
Comment on attachment 8570576 [details] [diff] [review]
1137398.patch
Thanks Giovanny! This looks good to me.
Flagging :baku to review as well, as we need an official DOM peer to sign off on any webidl changes.
Giovanny, do you have permissions to push to try? We'll need a try build before we can land.
Attachment #8570576 -
Flags: review?(bkelly)
Attachment #8570576 -
Flags: review?(amarchesini)
Attachment #8570576 -
Flags: review+
Assignee | ||
Comment 3•10 years ago
|
||
Yes I have, could you tell me the computed syntax for this?
Flags: needinfo?(bkelly)
Reporter | ||
Comment 4•10 years ago
|
||
Sure. I would use this syntax:
try: -b do -p all -u all[x64] -t none
This will build on all platforms, but only run tests on the linux64. Its what we call a "t-shaped" try build.
For future reference you can use the trychooser to generate the syntax:
http://trychooser.pub.build.mozilla.org/
The checkboxes for "Restrict tests to platform(s)" is the part that lets you only run tests on one platform, etc.
Flags: needinfo?(bkelly)
Comment 5•10 years ago
|
||
Comment on attachment 8570576 [details] [diff] [review]
1137398.patch
Review of attachment 8570576 [details] [diff] [review]:
-----------------------------------------------------------------
looks good to me!
Attachment #8570576 -
Flags: review?(amarchesini) → review+
Assignee | ||
Comment 6•10 years ago
|
||
Ben, check the link to treeherder:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=24710bc1cc2e
Let me know if you need something else
Reporter | ||
Comment 7•10 years ago
|
||
Once that looks green you can add the checkin-needed keyword to the bug. Then one of the sheriffs will commit it for you. (Unless you have L3 access and want to push yourself, of course.)
Assignee | ||
Comment 8•10 years ago
|
||
I have no L3 access, so I will wait for green status flag.
Thanks for the quick review and feedback.
Assignee | ||
Comment 9•10 years ago
|
||
Ben, Try server is almost done, could you check it and see if it could be landed?
Thanks
Flags: needinfo?(bkelly)
Reporter | ||
Comment 10•10 years ago
|
||
It looks like the failures you have are either known intermittents or infrastructure failures. I marked them as such.
I'll add the checkin-needed flag.
Thanks!
Flags: needinfo?(bkelly)
Keywords: checkin-needed
Assignee | ||
Comment 11•10 years ago
|
||
Thank you
Comment 12•10 years ago
|
||
Assignee: nobody → gioyik
Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox39:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla39
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•