Closed
Bug 610507
Opened 14 years ago
Closed 14 years ago
Get rid of the nsjetpack package
Categories
(Add-on SDK Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: avarma, Assigned: avarma)
References
Details
Attachments
(1 file)
The nsjetpack package contained in packages/nsjetpack isn't being used anymore; it hasn't been compiled for firefox 4, and odds are that changing it to work with firefox 4 would be either difficult or pointless, depending on the functionality. The "flexible membrane" functionality in it is mostly useless given the addition of JS Proxies to SpiderMonkey, and the memory profiling functionality likely needs to be changed a lot to work with JS compartments. Furthermore, even finding memory leaks using the profiler in firefox 3.6 was problematic given bug 592180. So we're probably just best removing the code from the tree for now, and bringing it back later if and when we decide to revamp the memory profiling code to work with the latest version of Gecko.
Comment 1•14 years ago
|
||
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product. To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
Assignee | ||
Comment 2•14 years ago
|
||
Assignee | ||
Updated•14 years ago
|
Attachment #492730 -
Flags: review?(myk)
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → avarma
Updated•14 years ago
|
Attachment #492730 -
Flags: review?(myk) → review+
Comment 3•14 years ago
|
||
https://github.com/mozilla/addon-sdk/commit/68b6e306dfeccef103b071e0812dc3a375830ac0 https://github.com/mozilla/addon-sdk/commit/715cb47c720bcdd11846cae6c6cab325bb1a982b https://github.com/mozilla/addon-sdk/commit/0e23d1c1555d5de228ed7ad62c8715e2775d2390
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•