Closed
Bug 455264
Opened 16 years ago
Closed 16 years ago
Leaking 1 nsRunnable + 1 nsThread, "loading" --chrome or --browser-chrome (tests)
Categories
(Testing :: Mochitest, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: sgautherie, Unassigned)
References
Details
(Keywords: memory-leak)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1b1pre)
Gecko/20080912014358 Minefield/3.1b1pre] (home, optim default) (W2Ksp4)
It is (often) enough to load the --browser-chrome (test) environment then close the two windows to see this leak.
Running any of the test makes it even more reproducible.
NB: The leak happens "almost always".
PS:
After the test part is completed, I have to Ctrl+C to exit Python.
I think this is unrelated, but mentioning it just in case.
Reporter | ||
Comment 1•16 years ago
|
||
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1b1pre)
Gecko/20080912014358 Minefield/3.1b1pre] (home, optim default) (W2Ksp4)
Same (at least) when running --chrome tests.
Summary: Leaking 1 nsRunnable + 1 nsThread, "loading" --browser-chrome (tests) → Leaking 1 nsRunnable + 1 nsThread, "loading" --chrome or --browser-chrome (tests)
Reporter | ||
Comment 2•16 years ago
|
||
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1b1pre) Gecko/20080915194703 Minefield/3.1b1pre] (home, optim default) (W2Ksp4)
R.WorksForMe: I don't know what fixed it.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Target Milestone: --- → mozilla1.9.1b1
Updated•16 years ago
|
Component: Testing → BrowserTest
Product: Core → Testing
QA Contact: testing → browsertest
Target Milestone: mozilla1.9.1b1 → ---
Version: Trunk → unspecified
Assignee | ||
Updated•7 years ago
|
Component: BrowserTest → Mochitest
You need to log in
before you can comment on or make changes to this bug.
Description
•