Re: Fwd: [Bug 784193] Thunderbird leaks threads

On 02/01/2013 09:11 AM, Stefan Sitter wrote:
> On 31.01.2013 16:37, Orion Poplawski wrote:
>> Any thoughts?
>
>  From a quick search [1] in the latest Lightning 2.3 source code I think there
> is only one place [2] that creates a thread in calICSService::ParseICSAsync()
> via NS_NewThread().
>
> How to tell if this thread is leaked?
>
> [1] http://mxr.mozilla.org/comm-central/search?string=thread&find=/calendar/
>
> [2]
> http://mxr.mozilla.org/comm-central/source/calendar/base/src/calICSService.cpp#1264
>

As noted in the bug, it seems most of the threads have to do with event 
processing:

#5  nsEventQueue::GetEvent (this=0x7f5d244fa390, mayWait=true, 
result=0x7f5d1d0fedf8) at 
/usr/src/debug/thunderbird-17.0.2/comm-release/mozilla/xpcom/threads/nsEventQueue.cpp:51
#6  0x00007f5d36156878 in nsThread::ProcessNextEvent (this=0x7f5d244fa340, 
mayWait=true, result=0x7f5d1d0fee3f) at 
/usr/src/debug/thunderbird-17.0.2/comm-release/mozilla/xpcom/threads/nsThread.cpp:605
#7  0x00007f5d3612c82b in NS_ProcessNextEvent_P (thread=<optimized out>, 
mayWait=true) at 
/usr/src/debug/thunderbird-17.0.2/comm-release/objdir/mozilla/xpcom/build/nsThreadUtils.cpp:220


I know nothing about this code, but perhaps threads can be created to process 
events?  Perhaps something is not setting them up properly?  I wonder if there 
is a way to see what created the event and event processor.


-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA, Boulder Office                  FAX: 303-415-9702
3380 Mitchell Lane                       [email protected]
Boulder, CO 80301                   http://www.nwra.com