WARNING: leaking reference to nsTimerImpl

RESOLVED INACTIVE

Status

()

Core
XPCOM
RESOLVED INACTIVE
10 years ago
a day ago

People

(Reporter: bc, Unassigned)

Tracking

({memory-leak})

Trunk
x86
Linux
memory-leak
Points:
---
Bug Flags:
in-testsuite +
in-litmus -

Firefox Tracking Flags

(Not tracked)

Details

These tests also give:

WARNING: An event was posted to a thread that will never run it (rejected): file c:/work/mozilla/builds/1.9.0/mozilla/xpcom/threads/nsThread.cpp

Does that need a new bug?

Comment 2

10 years ago
The first warning is bogus given that if nsTimerImpl::PostTimerEvent fails, the weak pointer to the timer that's stored in the created event is released (from the fix for bug 420521).  The warning is only valid if the timer runs, but it's not here; we should remove it.

The second is the real problem, but it's not obvious from the code what's wrong -- real question is who's posting the event to a dead thread, since that's the only way to trigger the second warning.  It's possible the OOMing nature of those tests plays a factor here, but it's hard to tell exactly how.

Comment 3

a day ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: a day ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.