Closed
Bug 556942
Opened 16 years ago
Closed 16 years ago
incorporate memory profiler
Categories
(Add-on SDK Graveyard :: General, defect)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
0.3
People
(Reporter: myk, Assigned: avarma)
References
Details
We should incorporate the memory profiler from the Jetpack Prototype into the SDK so that developers can find out how much memory their extensions are using and whether their extensions are leaking any memory.
Atul has said he's going to take this on for the 0.3 release, so setting the assignee and target milestone fields appropriately.
| Assignee | ||
Comment 2•16 years ago
|
||
Pushed:
Added nsjetpack binary component, which fixes bug 556942. While this currently contains more than just the memory profiling functionality, removing the extra flexible membrane and miscellaneous functionality would require recompiling this binary component for two versions of Firefox on 3 different platforms, which is a huge pain.
By Atul Varma (varmaa@toolness.com)
http://hg.mozilla.org/labs/jetpack-sdk/rev/2a4b985dafe0f678c5a4670e68e0f3c41a875d38
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 3•15 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
You need to log in
before you can comment on or make changes to this bug.
Description
•