Closed
Bug 581191
Opened 15 years ago
Closed 14 years ago
leaks when testing against Firefox
Categories
(Add-on SDK Graveyard :: General, defect)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: myk, Unassigned)
Details
I see a bunch of objects being leaked when testing against Firefox (both trunk and branch) on Windows, Mac, and Linux:
--------------------------------------------------------------------------------
warning: LEAK [object Object]
warning: LEAK [object Object]
warning: LEAK [object Object]
warning: LEAK [object Object]
warning: LEAK [object Object]
warning: LEAK [object Object]
warning: LEAK resource://testpkgs-jetpack-core-lib/memory.js
warning: LEAK resource://testpkgs-jetpack-core-lib/unload.js
warning: LEAK resource://testpkgs-jetpack-core-lib/unit-test.js
warning: LEAK resource://testpkgs-jetpack-core-lib/timer.js
warning: LEAK resource://testpkgs-jetpack-core-lib/xpcom.js
warning: LEAK resource://testpkgs-jetpack-core-lib/file.js
warning: LEAK resource://testpkgs-jetpack-core-lib/byte-streams.js
warning: LEAK resource://testpkgs-jetpack-core-lib/text-streams.js
warning: LEAK resource://testpkgs-nsjetpack-tests/test-legacy-nsjetpack.js
warning: LEAK resource://testpkgs-nsjetpack-tests/test-nsjetpack.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-api-utils.js
warning: LEAK resource://testpkgs-jetpack-core-lib/api-utils.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-app-strings.js
warning: LEAK resource://testpkgs-jetpack-core-lib/app-strings.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-byte-streams.js
warning: LEAK resource://testpkgs-jetpack-core-lib/url.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-collection.js
warning: LEAK resource://testpkgs-jetpack-core-lib/collection.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-context-menu.js
warning: LEAK resource://testpkgs-jetpack-core-lib/context-menu.js
warning: LEAK resource://testpkgs-jetpack-core-lib/xul-app.js
warning: LEAK resource://testpkgs-jetpack-core-lib/window-utils.js
warning: LEAK resource://testpkgs-jetpack-core-lib/errors.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-cuddlefish.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-errors.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-file.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-globals.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-localization.js
warning: LEAK resource://testpkgs-jetpack-core-lib/self.js
warning: LEAK resource://testpkgs-jetpack-core-lib/traceback.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-memory.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-observer-service.js
warning: LEAK resource://testpkgs-jetpack-core-lib/observer-service.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-page-worker.js
warning: LEAK resource://testpkgs-jetpack-core-lib/page-worker.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-plain-text-console.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-preferences-service.js
warning: LEAK resource://testpkgs-jetpack-core-lib/preferences-service.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-private-browsing.js
warning: LEAK resource://testpkgs-jetpack-core-lib/private-browsing.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-request.js
warning: LEAK resource://testpkgs-jetpack-core-lib/request.js
warning: LEAK resource://testpkgs-jetpack-core-lib/xhr.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-securable-module.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-selection.js
warning: LEAK resource://testpkgs-jetpack-core-lib/selection.js
warning: LEAK resource://testpkgs-jetpack-core-lib/tab-browser.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-simple-storage.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-tab-browser.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-tabs.js
warning: LEAK resource://testpkgs-jetpack-core-lib/tabs.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-text-streams.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-timer.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-traceback.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-unit-test.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-unload.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-url.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-widget.js
warning: LEAK resource://testpkgs-jetpack-core-lib/widget.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-window-utils.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-xhr.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-xpcom.js
warning: LEAK resource://testpkgs-jetpack-core-tests/test-xul-app.js
warning: LEAK resource://testpkgs-test-harness-tests/test-packaging.js
warning: LEAK resource://testpkgs-test-harness-tests/test-self.js
warning: LEAK resource://testpkgs-nsjetpack-lib/nsjetpack.js
warning: LEAK resource://testpkgs-jetpack-core-lib/plain-text-console.js
warning: LEAK resource://testpkgs-jetpack-core-lib/securable-module.js
warning: LEAK [object Object]
--------------------------------------------------------------------------------
The leaks don't show up when testing against XULRunner (which runs many fewer tests).
| Reporter | ||
Comment 1•15 years ago
|
||
Atul and Drew: any idea what these might be about?
Comment 2•15 years ago
|
||
If I disable all the tests in test-window-utils.js, for example, and run "cfx testpkgs -F window", I see a subset of the leaks above.
Comment 3•15 years ago
|
||
Hrm. If I disable the widget tests, and run those, I *don't* get any leaks.
Comment 4•15 years ago
|
||
Ok, maybe tracked down the big leak to the private browsing tests.
Comment 5•15 years ago
|
||
disable all private browsing tests and run *all* tests: no leak
enable just one private browsing test (any one will do) and run *all* tests: leaks the whole jetpack world
disable all private browsing tests and run *only* the private browsing tests: leak a subset of the jetpack world
| Reporter | ||
Comment 6•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
Comment 7•15 years ago
|
||
Whats the status of this bug? I still saw leaks running jetpack tests against mozilla-central trunk today.
| Reporter | ||
Comment 8•14 years ago
|
||
We're no longer generating these leak stats, but we're tackling leaks in more specific bugs like bug 642306 and bug 642430, so this bug is no longer useful.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•