Last Comment Bug 711838 - Remove the jetpack service
: Remove the jetpack service
: addon-compat, dev-doc-complete
Product: Core
Classification: Components
Component: JavaScript Engine (show other bugs)
: Trunk
: All All
-- normal (vote)
: mozilla12
Assigned To: :Ms2ger (⌚ UTC+1/+2)
: Jason Orendorff [:jorendorff]
Depends on: 713504
  Show dependency treegraph
Reported: 2011-12-18 08:09 PST by :Ms2ger (⌚ UTC+1/+2)
Modified: 2012-04-24 11:23 PDT (History)
10 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

Patch v1 (122.23 KB, patch)
2011-12-19 11:02 PST, :Ms2ger (⌚ UTC+1/+2)
benjamin: review+
Details | Diff | Splinter Review

Description User image :Ms2ger (⌚ UTC+1/+2) 2011-12-18 08:09:15 PST
It was disabled in bug 629197, and gal seems to really like the idea of removing it altogether.
Comment 1 User image Andreas Gal :gal 2011-12-18 08:23:46 PST
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 User image :Ms2ger (⌚ UTC+1/+2) 2011-12-19 11:02:13 PST
Created attachment 582884 [details] [diff] [review]
Patch v1
Comment 3 User image Myk Melez [:myk] [@mykmelez] 2011-12-19 16:46:49 PST
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.
Comment 4 User image :Ms2ger (⌚ UTC+1/+2) 2011-12-24 04:32:02 PST

Does this need to be announced somewhere?
Comment 5 User image Andreas Gal :gal 2011-12-24 10:08:24 PST
The jetpack service has been disabled (hard, at the C++ level, without config switch) for 9 month. I don't think anyone cares.
Comment 6 User image Teemu Mannermaa (:wicked) 2011-12-29 13:10:09 PST
(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?
Comment 7 User image Jorge Villalobos [:jorgev] 2012-02-23 12:05:55 PST
There are a number of old Jetpack add-ons still using this service.

Jeff, you might want to contact these developers.
Comment 8 User image Luke Wagner [:luke] 2012-02-23 12:09:16 PST
How would they be using it if it hasn't been compiling as part of FF for 9 months?
Comment 9 User image Jorge Villalobos [:jorgev] 2012-02-23 12:54:46 PST
They're most likely broken, but they will still install in Firefox 10 and above because they have Firefox 4 compatibility.
Comment 10 User image Jeff Griffiths (:canuckistani) (:⚡︎) 2012-02-23 12:58:21 PST
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.
Comment 11 User image Jeff Griffiths (:canuckistani) (:⚡︎) 2012-02-23 13:20:49 PST
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
Comment 12 User image Eric Shepherd [:sheppy] 2012-04-24 11:23:17 PDT
Noted here:

Note You need to log in before you can comment on or make changes to this bug.