Closed
Bug 427267
Opened 16 years ago
Closed 3 years ago
mochitest sometimes fails with "An event was posted to a thread that will never run it"
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: ajschult784, Unassigned)
Details
(Keywords: hang)
Sometimes running mochitests, I hit: WARNING: An event was posted to a thread that will never run it (rejected): file /home/andrew/tbox/SeaMonkey-mochi/Linux_2.6.22.14-72.fc6_Depend/mozilla/xpcom/threads/nsThread.cpp, line 359 WARNING: leaking reference to nsTimerImpl: file /home/andrew/tbox/SeaMonkey-mochi/Linux_2.6.22.14-72.fc6_Depend/mozilla/xpcom/threads/nsTimerImpl.cpp, line 464 ... and then the tests stop running. I have to quit SeaMonkey or wait for runtests to timeout. I suspect this happens occasionally on the FF tboxes but they don't build debug, so it just shows up as a mystery hang. This probably also happens outside of mochitest, but the app remains usable, so nobody notices.
Comment 1•16 years ago
|
||
If you can get a decent test case, that consistently reproduces the hang, then great. 'Til then -'ing.
Flags: blocking1.9? → blocking1.9-
the warning is from bug 404870
Comment 3•3 years ago
|
||
Closing this as resolved:incomplete due to lack of activity on this issue. If this is still relevant for today's Firefox version, please do re-open it.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•