[ wxwindows-Bugs-1523302 ] Thread keeps trying to be killed

[SourceForge.net]

Bugs item #1523302, was opened at 2006-07-16 09:44
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1523302&group_id=9863

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Thread
Group: Fatal
Status: Open
Resolution: None
Priority: 5
Submitted By: Steven Van Ingelgem (g00fy)
Assigned to: Nobody/Anonymous (nobody)
Summary: Thread keeps trying to be killed

Initial Comment:
thread.cpp @ 781:

When I Delete() my thread, the evtloop == NULL.
The call to '::MsgWaitForMultipleObjects' returned 
'WAIT_OBJECT_0 + 1'. But because of the evtLoop already 
deleted, it says like 'no eventloop, so no quit event' 
-> try again...

The reason why the eventloop = NULL is because in OnRun 
() this is set to the current one at the start, and at 
the exit of the OnRun() function it is set to the 
previous one (NULL).

Now AFTER you have the OnRun() function, you have the 
destruction of the 'CallOnExit' class, which calls 
OnExit() [init.cpp @ 431]...

And because my threads in my program are like 'global' 
threads (they are not depending on the wxFrame, but are 
just floating around, and being Delete() in wxApp::
OnExit()), they will never be killed and my program 
hangs indefinetly because the eventloop is already 
gone...

Hope that helps to fix this issue.


Greetings,
Steven

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1523302&group_id=9863