Remove the jetpack service

RESOLVED FIXED in mozilla12



8 years ago
7 years ago


(Reporter: Ms2ger, Assigned: Ms2ger)


({addon-compat, dev-doc-complete})

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)



(1 attachment)

It was disabled in bug 629197, and gal seems to really like the idea of removing it altogether.

Comment 1

8 years ago
This seems like a good deed in light of our linking-libxul-troubles. Myk, did you guys decide whether you ever want this kind of service? (I remember we talked about jetpack using a document-like execution environment, which this service isn't so suitable for).

Comment 2

8 years ago
Posted patch Patch v1Splinter Review
Assignee: general → Ms2ger
Attachment #582884 - Flags: review?(benjamin)
bholley, ejpbruel, and I chatted about this on IRC today.

The upshot: it's fine to remove the jetpack service, since the Jetpack project has puts its e10s efforts on hold, and if/when we do pick up that project again, it doesn't seem likely that we'll use jetpack processes to implement out-of-process addons, as we were leaning toward using content processes anyway.

If we change our minds, we can always retrieve the code from the repository history.


8 years ago
Attachment #582884 - Flags: review?(benjamin) → review+

Comment 4

8 years ago

Does this need to be announced somewhere?
Last Resolved: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla12

Comment 5

8 years ago
The jetpack service has been disabled (hard, at the C++ level, without config switch) for 9 month. I don't think anyone cares.
Depends on: 713504
(In reply to Ms2ger from comment #4)
> Does this need to be announced somewhere?

Maybe update or somewhere around there that this is no longer available at all?
Keywords: dev-doc-needed
There are a number of old Jetpack add-ons still using this service.

Jeff, you might want to contact these developers.
Keywords: addon-compat
How would they be using it if it hasn't been compiling as part of FF for 9 months?
They're most likely broken, but they will still install in Firefox 10 and above because they have Firefox 4 compatibility.
Those add-ons are using pre-1.0 SDK code, IMO this is another case where we will need to contact developers direectly, but also unfortunately also a case where the SDK apis may have changed.
Further, I honestly think we should do the following:

* Identify the affected add-ons
* make them incompatible with Firefox 10
* contact the authors and explain what we did, why, and encourage them to re-pack with 1.5
You need to log in before you can comment on or make changes to this bug.